MASAV Return Files: Reading Them Automatically and Updating Customer Balances

A return file is not a blanket statement that collection failed. It is new information received after an earlier debit, and it must be linked to the original debit, authorization, and customer balance without deleting history. MASAV publishes specifications for charge-return files and offers a service for receiving information on debits that were not honored.

The usual mistake is to mark an invoice “unpaid” as soon as the file arrives, or to send a new collection message without checking whether the customer paid by another method. Each return row should create an event containing the original debit ID, returned reason, date, amount, and customer link.

Statuses that preserve the truth

Keep the original debit as “transmitted” or “collection attempted.” Create a separate “returned” result with its reason. Only an approved business rule decides whether to reopen a balance, pause a subscription, create a collection task, or request details. This also makes an import mistake reversible without charging twice.

Import into a review queue, reconcile by original debit ID rather than amount alone, and expose exceptions: missing debit, differing amount, customer already settled, or a file already processed. Update the operational system only after those results are approved.

Source

MASAV file specifications