Start with the accounting question
For a bookkeeper, the useful question is not how many cards were distributed. It is whether the wages approved for a pay period can be traced through the employer’s liability, cash movement and exception records. Fintwist is now described by its provider as Corpay Prepaid. A card product can be one destination for net pay, but its marketing page does not define a particular employer’s report layout or settlement terms. Use the actual payroll, bank and contracted provider records before marking a payment reconciled.
Separate three amounts in the workpaper: gross wages and deductions from the payroll register, net pay assigned to each disbursement method, and the amount that left the funding account. The first is a calculation, the second an instruction and the third cash evidence. A single green status in a payroll application may cover only one of those boundaries. Record which source, date and responsible person establishes each amount.
WATCH & UNDERSTAND · 32 SECONDS
Four records, four different claims
Original visual explainer · silent · no autoplay
A silent illustration of approved wages, instruction, funding and exception evidence. This is an editorial illustration, not a provider tutorial or a recording of an account. Video files are served by this website.
Read the full video explanation
- 01 / APPROVAL. Approved wage. The register establishes the calculated amount, not delivery.
- 02 / ROUTE. Method instruction. Identify the intended destination and effective run.
- 03 / CASH. Bank movement. Match the debit to the actual batch; timing may differ.
- 04 / REVIEW. Open difference. Keep rejected items and corrections visible.
Source context: IRS employment tax recordkeeping. The visual arrangement and hypothetical examples are editorial explanations.
Build a traceable set of identifiers
A practical workpaper keys each payroll period to a run identifier, bank transaction reference, disbursement batch and exception log. These are internal bookkeeping fields for the employer, not a claim that Corpay exposes identical fields in every program. Ask the payroll vendor and provider what identifiers actually appear in the contracted exports. When the names differ, maintain a documented crosswalk rather than forcing an apparent match by amount alone.
For an illustrative $32,000 net-pay run, $8,000 could be assigned to cards, $22,000 to workers’ own accounts and $2,000 to another lawful method. The $8,000 allocation does not show that $8,000 posted to cards. Match the corresponding funding debit and the provider’s accepted and rejected items according to the agreement. The example is hypothetical; there is no published universal Fintwist settlement timeline or fee in this guide.
Investigate a difference without erasing history
Suppose the card allocation is $8,000 but the accepted report lists $7,850 and one $150 item is rejected. Flag that item against a case owner, its funding treatment and the eventual correction. Do not simply change the historical allocation to $7,850, because the approved wages and the attempted disbursement are distinct records. Determine whether the $150 remains an unpaid wage obligation, an amount returned to the employer or an item pending resolution under the actual provider arrangement.
A correction should link the original payroll register, provider response, bank movement and replacement payment. If someone resends the entire file, duplicate pay can be created; the finance reviewer should ask which individual instruction is being replaced and whether the original is still in progress. Where an employee says pay is missing, refer the wage issue to the employer’s payroll team. This publication does not view accounts or accept employee credentials.
Close the run with a documented explanation
At close, write one sentence for each unresolved difference: what disagrees, the exact records examined, who is investigating, and when the next check occurs. A variance list without ownership is not a completed reconciliation. Keep the document set under the employer’s approved access controls, because it can contain wage and account routing information. A public article is no substitute for a secure payroll ledger.
For the next step, compare funding to accepted instructions, then work through rejected payments. The IRS employer recordkeeping guide and Department of Labor fact sheet describe distinct federal recordkeeping duties; this editorial workpaper is a suggested control, not a declaration that those agencies require its exact columns.
When totals agree for the wrong reason
Suppose a $120 item is rejected and a second $120 item is accidentally sent twice. The aggregate disbursement total might still equal the approved allocation even though two employees have opposite problems. Reconcile at the item level when that evidence is legitimately available, and keep a separately reviewed exception population when it is not. A pleasing total must never be described as proof that every instruction was correct. Record any privacy limit on the sample reviewed so a later reader understands the scope.
Look for unmatched negative entries and reversals, not only outgoing amounts. A returned batch may arrive days after the original debit, and a corrected wage payment can be posted under a different method. Tie those movements to the same case rather than treating a credit as unrelated income. This makes the general ledger balance more informative while leaving the question of an employee’s actual account access to the authorized parties.
A four-column evidence matrix
The first column names the employer’s claim: “these wages were calculated,” “this method was selected,” “this instruction was accepted,” or “this money moved.” The second names the record that could prove it. The third names the system or custodian of that record, and the fourth names any open exception. Keeping the claim separate from its evidence prevents a printed payroll register from being reused as proof of an account posting. In a meeting, ask the team to fill the matrix for one ordinary item and one failed item rather than debating the semantics of “paid” in the abstract.
For a simple successful-looking run, the register may confirm approved net pay, a method file may show the intended card destination, and a bank debit may support funding. A provider acknowledgment still has to be interpreted according to its actual status definition. If it confirms receipt rather than posting, the workpaper should say so. The accountant can present a careful conclusion about the records available without overstating what the worker could see. This is especially useful when payroll staff and finance staff use different words for the same checkpoint.
Make the total reconcile to the population
Totals can be correct while the population is wrong. Compare the count and identity of card-directed records in the approved register with the count and identity in the submitted instruction set. If one employee changed wage method after cutoff, the reason for the difference should be documented. Avoid moving an unmatched amount into “rounding” or “miscellaneous” when it represents a whole wage instruction. A population check does not require publishing the list on an open website; it belongs in a restricted internal review.
Next match accepted, rejected and pending items against the submitted set, then compare the related funding and returns to bank activity. A provider’s reports may support different levels of detail, so the review method must reflect the actual contracted data. If only a total is available, mark item-level confirmation unavailable rather than inventing it. The reviewer can then decide whether an authorized additional report, a sampling approach or a different control is needed for that employer.
Do not merge accounting and compliance conclusions
A card-channel funding balance can reconcile perfectly while wage-choice paperwork is defective. Conversely, complete employee choices do not show that the associated funds moved. The CFPB guidance on alternatives explains the broad federal choice issue, with state rules affecting the details; the accountant needs the employer’s relevant policy and selection records for that separate question. A finance sign-off should describe its own scope instead of silently claiming to certify employee consent, fee disclosures or every state wage requirement.
The same separation matters for taxes. The IRS describes an employer’s employment tax records; a net-pay funding debit does not prove gross wages or withholding. The DOL describes wage records and retention. Keep a link from the payroll calculation to the disbursement evidence while preserving the different reasons those records exist. When a discrepancy touches taxes or legal wage timing, send the actual record set to people authorized to make that determination.
What a useful exception register contains
One line should identify the affected run and instruction, approved net amount, exception state, cash position, owner, next action and eventual resolution record. The description should use the status supplied by the system that produced it, such as “provider file accepted” or “bank return received,” not a vague label like “fixed.” Include timestamps, but do not assume that a business-day cutoff in one system has the same timezone as another. If statuses later change, preserve the earlier observation and record when the new one was learned.
Review the open register at the next payroll cycle and month end. An unresolved item can otherwise become a reconciling difference that is copied indefinitely. Before closing it, verify both a suitable wage-resolution record and a cash-resolution record, which may be different documents. The employer should follow its actual agreement and laws for the correction. This site proposes a transparent evidence habit; it cannot authorize a payment, confirm a balance or determine a particular worker’s legal claim.
The check to carry forward
Can an independent reviewer connect the approved wage, intended destination, cash evidence and unresolved item without consulting a private conversation? Record the answer beside the source document, date and owner. If the evidence does not exist, list the missing item as an open question; do not convert the absence into a successful reconciliation. This disciplined distinction is the point of an employer-side accounting file, and it is the limit of what an independent article can suggest without the underlying program records.