Create and submit a transaction

An immediate Transaction is a double-entry posting for the current company working day. It can contain several batches, but every batch must balance in the company base currency before it can be saved.

Access required

You need Create Transaction and access to the selected booking Branch. The Transactions list and saved record require Read Transaction.

Entering a Manual, Central Bank, or Third-Party rate also requires Override FX Rate. Saving or submitting can be further restricted by a matching conditional access policy.

Before you begin

Complete Before processing the first transaction. Confirm the correct debit and credit Accounts, Transaction Codes, currencies, amounts, and supporting reference before capture.

Create the transaction

1. Open Customer Relationship → Transactions → Transactions.
2. Select Create Transaction. The screen is titled New Transaction.
3. At L0, select the Company.
4. On Header, confirm the Posting Date and select the Value Date, Branch, optional Narrative, and Intent.
5. Under Posting Lines, select the Transaction Code for Batch 1 and confirm the optional Cost Centre, then optionally enter a Batch Narrative.
6. Add the required debit and credit Accounts, select each line's transaction currency, and enter a positive amount.
7. Add debit or credit lines as needed. Select Add Batch when another Transaction Code is required.
8. Confirm that every batch shows balanced debit and credit totals in the base currency.
9. Select Save as Draft or Save & Submit.
10. Review the Commission Fee Review when it appears, record an explicit Apply or Waive decision for every applicable fee, then confirm the action.

The transaction may contain no more than 50 lines across all batches. Lines are part of the parent Transaction and are not maintained separately.

Header choices

Dates

Posting Date is read-only and uses the selected company's current working day. Value Date controls when the posting takes effect for value-dated processing such as interest accrual. It cannot be after the Posting Date; use a Forward-Dated Transaction for future execution.

Booking Branch

Branch is the initiating and booking Branch for the entire transaction. For a branch-scoped user, it must be one of the user's accessible Branches. Accounts from other Branches may still be included in the lines; their Branches do not replace the header booking Branch as the transaction's scope boundary.

Intent

The normal choice is General Posting. The form also exposes:

• Group Contribution, which requires the line shape to identify an active Group member and Group plus the applicable contribution type and balance bucket;
• Loan Repayment, which is used by the supported loan-repayment journey.

Other system-generated transaction purposes are not selectable from this generic form.

Posting batches and lines

Each batch represents one independently balanced use of a Transaction Code. All lines in that batch inherit the selected code. A batch requires at least one Debit and one Credit line and at least two lines in total.

Cost Centre is recorded at batch level. A new batch defaults to the acting user's current Cost Centre when one is assigned, but it can be changed or left unassigned. Posting lines store the selected Cost Centre Code and Name as an immutable snapshot. Reassigning the user or renaming the Cost Centre later does not rewrite the posted transaction.

For each line:

• select an active Authorized Account;
• leave the line currency as the Account currency or choose another enabled company currency;
• enter the amount in the selected line currency;
• review the Account-currency and base-currency equivalents when conversion is required.

remoteEaze validates the Account and Transaction Code again on the server. It also checks transaction-intent rules and available Account or Facility capacity before final authorization.

Save or submit

Save as Draft creates a Captured record without starting approval. Open the record and select Edit to continue; the edit form provides Save & Submit.

Save & Submit creates and submits the transaction as one operation. A successful submission either:

• moves to the first required approval stage, starting with L3 when three levels are required; or
• becomes Authorized immediately when no approval level is required.

Authorization queues the ledger posting. Processing remains Pending until that posting completes, then becomes Processed or Failed. Continue with Review and authorize transactions.