Processors and file formats
Two processors are read the moment a file lands. Every other layout is mapped once — you point at the columns, and each later month reads itself. Accepted as xlsx, xlsm, xls, csv.
Read on upload
No configuration. The file is recognized by its own shape, and the month is reconciled against it.
CardX
Card processing residuals
Reports the monthly fee collected per merchant
Fortis Cards
The card side of a Fortis book
Does not report a collected fee — shown as not reported, never as $0
Fortis GTWY ACH
The gateway ACH side, kept separate from card
Does not report a collected fee — shown as not reported, never as $0
Everything else, mapped once
Upload a file from any processor and point at its columns. Two are required — whatever identifies the merchant, and what you are actually paid on. Volume, transaction count, collected fee and the open date are taken when the file has them. From then on that processor's files load like a built-in one, and the mapping can be published so the next customer on the same processor does not repeat it.
A mapping mistake is the only failure in this product that produces a complete, plausible, wrong month — every other failure is loud. So an unreadable cell skips its row and says which row and why, rather than coercing it to zero.
Questions
- What if my processor is not one of these?
- You map it once. Upload a file, point at the column that holds the MID and the column that holds the residual, and every later month from that processor reads itself. Volume, transaction count, collected fee and the open date are optional — name them if the file has them.
- What happens to a row the mapping cannot read?
- It is skipped and reported, never guessed. A mapping mistake is the only failure here that can produce a complete, plausible, wrong month, so an unreadable cell stops that row and tells you which one and why, rather than coercing it to zero.
- Do files have to be uploaded by hand?
- No. Every workspace has an intake address, one per book when there are several. Forward the file your processor already emails you and it lands on Uploads with the sender recorded against it.
- What if a file arrives in a layout nobody has mapped yet?
- It is accepted and parked as needing a mapping rather than rejected, and the owners are told once that a file needs them. Nothing is dropped on the floor because its shape was unfamiliar.
What it costs is on the pricing page, and the terms are in the Terms of Service.