Moving from an older SOFTEX workflow: keep the audit trail

Inventory legacy export references and ask about transition handling without duplicating or erasing older submissions.

Changing the preparation process should not destroy the history of earlier exports. Old acknowledgements, bank references and unresolved balances can still be needed to understand a transaction. Before moving a recurring software-export routine, inventory what is already on record and what remains outstanding.

Build an opening-balance inventory

List legacy invoice references, declaration identifiers, receipts, adjustments and previous extensions. Mark whether each item is pending, acknowledged or confirmed closed using the evidence you hold. Keep unknown status visibly unknown. Do not recreate an old invoice as a new export just because the new worksheet has a different layout. Preserve the original files and create a separate transition index.

Ask how the authority wants the handover recorded

Send a focused enquiry describing the existing workflow and the new period. Ask which records continue under their existing references, what new format applies and how corrections should be handled. Request instructions before making duplicate submissions to multiple authorities. Keep a clear boundary between historical balances and newly issued invoices in your working schedule.

Inventory references before moving data

Start the transition with an opening list of invoices, old declaration identifiers, authority acknowledgements, receipt allocations and unresolved balances. Record the source location for each. A spreadsheet imported from an old system may carry only a short reference, while the original acknowledgement contains the fuller identifier needed by the bank. Preserve both and explain the relationship.

Distinguish an old export with a new receipt from a genuinely new export. The event occurring this month may be a payment, correction or follow-up on an earlier invoice. Do not reset the commercial date or recreate the full value as new revenue simply because the new template starts with an empty schedule. Keep the historical transaction attached to its original evidence.

Reconcile opening balances against actual evidence

Compare the legacy outstanding balance with invoices, allocated receipts and supported adjustments. Where the system status and your documents differ, identify the exact disagreement and ask the handling institution for clarification. Do not choose the status that produces a cleaner migration report. Keep unknown or disputed items in an exception list with the evidence needed to resolve them.

Select a sample of apparently closed items as well as pending ones. The purpose is to check that status labels have a consistent meaning, not to reopen everything. A bookkeeping balance of zero may lack the separate official confirmation your process needs. Keep that distinction in the transition index so the new routine does not inherit an unsupported blanket closed label.

Agree the handover boundaries with the authority

Describe the legacy workflow, the first new period and the outstanding items. Ask which references remain in use, how corrections are submitted and what new information or format is expected. If multiple institutions are involved, keep their roles and responses separately labelled. Do not treat a response from one desk as an instruction covering another authority’s records.

After receiving instructions, freeze the opening index and record later events as updates. Keep the old archive retrievable for the applicable record requirements. Train the person preparing the new schedule to recognise historical references and exceptions. A successful transition preserves traceability and clear ownership; it is not measured by how quickly the old folder can be deleted.

A fictional example

A software company has three older acknowledged records and one unresolved receipt match. Its transition list retains all four references. The bank’s response determines how the unresolved item is followed up; the company does not delete it when starting a new monthly file.

Preparation checklist

Preserve legacy acknowledgement identifiers.
Separate historical balances from new invoices.
Request written instructions before duplicate reporting.

Does a new form automatically cancel an earlier acknowledged record?

Do not assume that. Confirm transition and correction handling with the relevant authority.

FICTIONAL WALKTHROUGH

A new worksheet meets an older unpaid invoice

A fictional exporter has a legacy acknowledged invoice for USD 3,000 with USD 1,000 received. Its new preparation routine begins in October. The opening index keeps the original invoice date and acknowledgement, with USD 2,000 outstanding before other supported adjustments.
A further USD 500 arrives during the new period. The preparer records it as a receipt allocated to the older invoice, not a new USD 500 export. The bank enquiry identifies the historical reference and asks about the appropriate transition and matching process.
The institution’s response is linked to the opening index and later receipt. The new monthly file contains a historical-events view separate from new invoices. Earlier acknowledgements remain accessible, allowing a reviewer to follow the whole transaction across the process change.

Your next step

Read the historical-invoice guide

Sources and scope

Sources reviewed 9 October 2026. The routines and fictional examples are editorial preparation suggestions. They do not confirm your bank’s acceptance, classification or transaction status.

Suggest a correction with a supporting source