remoteEaze

Forward-dated transactions

How to schedule, authorize, monitor, and cancel a future transaction.

A Forward-Dated Transaction is an instruction that remoteEaze holds for a future date. It is authorized before execution, reserves the applicable Debit amount when authorization completes, and creates the actual Transaction when its execution date arrives.

Use this for a one-time future payment. Use a Standing Order when the same instruction must recur monthly.

Before you begin

Complete Before processing the first transaction. For this task, also confirm that the authorized working-day calendar covers the scheduled and roll-forward dates and that the Forward-Dated Transaction reference sequence is configured.

The current shared creation screen requires Create Transaction to enter and Create Forward Dated Transaction to enable scheduling, plus access to the Booking Branch. If you enter a manual FX rate, you also need Override FX Rate for Transactions. Reading, exporting, editing, deleting, and approving use their corresponding Forward Dated Transaction permissions.

Data access is determined by the header Booking Branch. Individual posting lines may use accounts from other branches.

Create and submit an instruction

  1. Open Operations → Customer Relationship → Transactions and select Create Transaction.
  2. Complete the Transaction Header and posting batches as described in Create a transaction.
  3. Open Schedule and turn on Schedule for later.
  4. Select the instruction Type:
    • Scheduled Payment for a general future payment;
    • Post-Dated Check for a post-dated-check instruction.
  5. Select a Scheduled Date after the company's current working day.
  6. Confirm the Working Day Policy. The current policy is Roll Forward: a weekend or holiday moves execution to the next configured working day.
  7. Select Save as Draft or Save & Submit.

Each posting batch needs an authorized Transaction Code, at least one Debit and one Credit, and equal Debit and Credit totals in the base currency. remoteEaze resolves account Products, account Branches, FX amounts, and the final execution date during validation.

Each batch can also carry a Cost Centre. It defaults from the maker when available and remains optional. The resolved Code and Name are frozen into the posting lines created at execution.

The Scheduled Date cannot be the current working day. remoteEaze enforces this rule when the instruction is created or its Scheduled Date is changed, not only in the creation screen.

Authorization and reservation

A submitted instruction follows its configured approval path, descending L3 → L2 → L1 when all three levels are required. The maker cannot approve their own instruction, and each approval stage must be completed by an eligible user with access to the Booking Branch.

The execution status remains Draft while approval is incomplete. On final authorization it becomes Scheduled, and remoteEaze reserves the applicable amount on each Debit account. The detail page shows the total reserved amount in the company's base currency and whether it is already locked or will be locked on approval.

If an approver rejects the instruction, the maker can open it, select Edit, correct it, and submit it again. A denied instruction is terminal.

Scheduled and resolved dates

Scheduled Date is the date requested by the maker. Resolved Execution Date is the working day on which remoteEaze will attempt execution. They are the same when the scheduled date is a working day; otherwise, the resolved date is the next configured working day.

When execution succeeds, the instruction becomes Executed and the detail page links to the resulting Transaction. Instructions generated by Standing Orders also show their Standing Order source.

Edit, delete, or cancel

  • A Captured or Rejected instruction can be edited before authorization.
  • Only a Captured draft can be deleted, using Delete Forward Dated Transaction.
  • A Draft or Scheduled instruction can be cancelled using Update Forward Dated Transaction. Enter an optional cancellation reason and confirm Cancel Instruction.
  • Cancelling a Scheduled instruction releases its Debit-account reservations.
  • Executed, Failed, and Cancelled instructions cannot be cancelled.

Cancellation keeps the instruction in history; it does not delete it.

Monitor instructions

Open Operations → Customer Relationship → Forward Dated. Search by reference or narrative, or filter by execution status, approval status, type, or company when company-wide access is available. Users with Export Forward Dated Transaction can export the records within their permitted scope.

Approval status and execution status answer different questions: approval status shows where the instruction is in maker-checker, while execution status shows whether it is Draft, Scheduled, Executing, Executed, Failed, or Cancelled.

On this page