Transaction operations

remoteEaze supports several transaction journeys. Choose the journey by when and how the posting should be produced:

• use an immediate Transaction for a balanced posting on the current working day;
• use a Forward-Dated Transaction for a one-time future instruction;
• use a Standing Order for a recurring instruction;
• use a Financial Upload to validate and authorize a controlled file of transactions.

This chapter covers the Dashboard journeys. For offline field capture, see Workbench transactions.

Immediate transaction journey

An immediate transaction is captured as one or more independently balanced posting batches. Each batch has one Transaction Code and at least one debit and one credit line. remoteEaze converts the lines to the company's base currency, records applicable commission decisions, and submits the complete transaction through maker-checker authorization.

Authorization and processing are separate:

1. Approval status progresses from Draft through any required L3, L2, and L1 stages to Authorized.
2. Processing status progresses from Pending to Processed after the authorized posting updates the ledger. A posting problem produces Failed.

The list at Customer Relationship → Transactions → Transactions shows both statuses. Do not treat Authorized as confirmation that ledger posting has finished; confirm that Processing is Processed.

Where to continue

• Create and submit a transaction
• Review and authorize transactions
• FX, fees, commissions, and rounding
• Correct or reverse a transaction

Complete Before processing the first transaction before beginning operational capture.