Before processing the first transaction

What this prepares

A permitted user can create a balanced ordinary transaction for the current business day, submit it through the required approvals, and send it for posting.

Required before first use

• An Authorized active financial working year has a coherent current working day. An ordinary transaction's posting date must equal that day and must not be a configured weekend or public holiday.
• The tenant has exactly the intended base currency, with currency precision available. Every other currency used by a line is configured for the tenant.
• The required transaction codes are Authorized and available in the transaction form.
• Every debit and credit account is Authorized. Its Account Status must allow the line's direction, and its currency precision must be available.
• The user can select the header Transaction Branch, and that booking branch is within the user's data-access scope.
• Each batch contains at least one debit and one credit and balances in local currency after any FX rounding line is resolved.

Complete Business calendar, Currencies, Transaction Codes, and Chart of Accounts before testing the operating form.

Access and authorization

• The maker needs Create Transaction and access to the header Transaction Branch.
• A user editing another maker's Captured or Rejected draft needs Update Transaction.
• Provide the exact Transaction L1, L2, and L3 authority required by the Create action and any matching access policy.
• Grant Override FX Rate only when a user may enter a non-system rate with the required rate source, reason, and supporting evidence.

Branch authorization uses only the header Transaction Branch. The branches of individual accounts and lines do not each have to be within the checker's branch set. See Data-access scope.

Required only when using this feature

• For cross-currency lines, configure effective exchange rates for the posting date and the supported rate types. Configure FX rounding products and accounts where the currency conversions can create a rounding difference.
• If a transaction code triggers a commission, configure and authorize the commission type, posting code, income account, bands, and payer rules.
• Configure product usage restrictions when departments or branches should be limited to particular products.
• Configure conditional access policies if transaction facts should change approval requirements or block a matched transaction.
• Use a Forward-Dated Transaction instead of an ordinary transaction when the value date is after the posting date.

Verify the setup

1. Sign in as the intended maker and open Customer Relationship → Transactions.
2. Select Create Transaction and confirm that the intended booking branch, authorized transaction code, and debit and credit accounts are available.
3. Enter a controlled same-currency batch and confirm that the balance indicator reaches zero.
4. Save and submit it. Confirm that the resulting status matches the resolved approval count.
5. Complete the required checker decisions and confirm that the transaction is eventually processed, not left failed or pending because posting reference data is missing.

See Create a transaction for the field instructions.