Same bank export every month
Keep the statement-to-GL map for the next cycle.
Recipes
A recipe stores mappings, matching rules, and workflow setup. The same bank export, vendor statement format, or client ledger structure does not need to be mapped again.
The second month should be cheaper than the first. Without a saved configuration, every period is a new mapping exercise and a new chance to pick the wrong amount column.
Sample preview
Conceptual. Your files will differ.
How it works
Step 1
Finish one good run with the columns and match types you trust.
Step 2
Store mapping, matching rules, and workflow type together.
Step 3
Upload the new files and start from the last good setup.
Step 4
If a column moved, edit the recipe once instead of rebuilding it.
What this workflow is designed to do with uploaded files.
Keep the statement-to-GL map for the next cycle.
Reuse invoice, credit, and amount columns across vendors that share a layout.
Firms keep a recipe per client instead of rediscovering headers.
Tolerances and match types are part of the recipe, not a sticky note.
January’s operating-account rec is saved as a recipe. In February the same two column maps and date tolerance apply. The analyst spends time on new outstanding items, not on finding the amount column again.
Recipes are how setup time drops after the first period. They are configuration, not an approval. A reused recipe still produces a new run that people can review.
Continue with the workflows that usually sit next to this one.
No. Each run is stored separately. The recipe only starts the next run.
Yes. Save one configuration per file layout.
Edit the recipe once. Later periods use the updated map.
Map once, store the recipe, and start the following period from that configuration.