Routable advertises bulk payment creation through CSV upload, including field mapping and alerts for duplicates or inconsistencies. Those features can help process a large run, but the finance team still needs to establish which obligations belong in the file and which rows were successfully handled. Source: Routable CSV payments.
The critical control is a traceable connection between each source obligation and its resulting payable. Without that connection, correcting a file can accidentally reintroduce items that were already accepted.
Use the correct current template
Obtain the template or import specification for the workflow you are actually using. Do not reconstruct required headers from an old screenshot or another company’s file.
Identify which fields are required, which values must match existing records, and how dates, amounts, and currencies should be represented.
Keep formatting changes under control. Spreadsheet software can alter dates, long identifiers, and leading zeros. Review the exported CSV itself where those changes could affect matching.
This guide provides a control method, not a substitute import schema.
Define the source of the run
Record where the payment obligations came from and which period the file covers.
Assign a stable reference to each obligation in the working process. A vendor name and amount alone may be insufficient when the same vendor has several similar bills.
Before export, remove items that should not be paid in this run. Examples include unresolved obligations, items already settled through another route, and records still awaiting required authorization.
Keep exclusions in a separate review record with a reason. Deleting a row without explanation makes the run harder to reconcile later.
Establish control totals
Record the row count and amount before upload. If more than one currency is involved, keep totals separate by currency.
For a hypothetical single-currency run, assume 100 intended payment rows total $10,000. If two rejected rows total $400, the remaining 98 rows should total $9,600.
These figures are an arithmetic illustration, not a Routable import result.
The check helps identify an unexplained difference. It does not prove that all 98 accepted rows contain the correct recipient or accounting information.
Review validation results by row
Investigate each rejected or flagged item. Determine whether the issue concerns formatting, a recipient match, an existing obligation, or another reported condition.
Routable advertises duplicate and inconsistency alerts. Treat an alert as a review prompt, not proof that every possible duplicate will be detected or that every flagged row is wrong. Source: Routable CSV capabilities.
Keep the result beside the source reference. This allows the team to distinguish a corrected row from an untouched row and an accepted row from one that still needs action.
Do not assume upload means payment delivery
Establish what the import action created and what remains before payment.
The run may still require approval, recipient readiness, scheduling, or another step under the configured workflow. Inspect the resulting records rather than inferring completion from a successful file upload.
The approval workflow guide and payment status guide explain the next stages.
A finance manager should be able to state how many obligations were imported, how many are authorized, and how many have progressed to delivery.
Handle corrections without resending accepted work
Before uploading a revised file, identify the disposition of every row from the earlier attempt.
Prepare the correction around unresolved items using the supported process. Do not assume that changing the filename prevents duplication or that re-uploading the complete original file is harmless.
If the result of the first import is unclear, investigate it before trying again. The task is to establish what already exists.
Retain the source version, review results, and resulting references together. That record helps another team member continue the run safely.
Reconcile the run after processing
Compare the original intended obligations with the resulting payables and exceptions. Explain every excluded, rejected, canceled, or unresolved item.
Then connect the payment results to accounting records through the integration and reconciliation guide.
A controlled CSV process ends with an explained disposition for every intended row. A file that uploaded successfully is only one milestone in that process.