A file named “Funding Complete” arrives at 4:58 p.m. The total matches the payroll register. Does it mean the funding debit happened, an instruction file passed validation, or each individual card load succeeded? Read the report’s definitions before you use its title to answer any of those questions.

Start from a dictionary you control

Maintain a mapping with a row for each status your operations team relies on. Record its provider definition and version, where it occurs, what evidence proves it and whether another event can follow. Include examples near the batch cutoff: a status may be final for a file upload but preliminary for a wage item. Keep the provider’s actual report names alongside your internal terms so a replacement reviewer can trace a decision after an update.

  • Received: In a sample dictionary, this means only that the upload entered the queue. It is not evidence that the payee received wages.
  • Accepted: Without a documented item-level definition, this might refer to a file rather than an individual instruction.
  • Returned: A reason code may explain how the instruction was rejected, but separately verify whether any prefunding was returned and how it appears at the bank.

These meanings are hypothetical, not descriptions of a specific live provider. In a sample file, 61 entries were received and 60 ultimately confirmed; the remaining $89 needs its own case. Reading the word “received” as “posted” would create a false $89 clearance.

Fin Twist in a historical file name

If an old internal archive uses the spaced shorthand “Fin Twist,” the provider’s public Corpay Prepaid overview can help explain why a current document may have different branding. Its public PayCard page describes the wage use case. It does not supply the report dictionary for your employer, convert a legacy program automatically, or prove which status codes and cutoffs governed a particular batch. Base that mapping on your authorized program materials and retained reports. This publication does not operate the program or have access to those materials.

Retire a term without erasing the evidence

When the format changes, compare a synthetic old report with an authorized example of the revised format before swapping the mapping. Preserve the earlier definition for already closed periods. Ask which identifier survives across the bank, report and accounting systems; if there isn’t one, document the lookup evidence rather than inventing a universal identifier. For old-period review, start with the audit sample walk-through; for active exceptions, use the close memo.