​
Configure file selection

Define the inbound path, filename pattern, format, campaign, workflow, schedule, and time zone. Use sortable names:
GetBill sorts matching filenames in descending alphabetical order and selects only one file: the first after that sort. The SFTP modification time does not affect this choice. There is no persistent file queue: selection is recomputed on every run. A correction must sort after the previous name. Upload under a temporary name that does not match the pattern, then rename it after transfer completes.

​
Handle missing files and deduplication

When there is no matching file, the run has no effect: no monthly campaign is created, no missing-reference reconciliation occurs, and no post-import export is generated. After a completed run that created or updated at least one debt, strictly identical content is skipped, even under another name. This deduplication does not apply to a failed run or one with no created or updated debt. Conversely, replacing the content under the same name technically produces new content. Always publish a correction under a new traceable filename that sorts after the previous one. In full_sync, that correction again represents the entire active scope.

​
Follow the format contract

​
CSV

  • UTF-8 with BOM;
  • semicolon (;) delimiter;
  • exactly one header row;
  • standard CSV quoting for separators, quotes, and line breaks.
Inbound detection also tolerates clearly structured comma-delimited files, but semicolons remain the contractual format and the GetBill export delimiter.

​
XLSX

The active Import sheet contains headers on row 1 and only data from row 2. Explanations remain in the Notes sheet. Never place a legend or total below the data rows. Use YYYY-MM-DD dates.

​
Follow the row contract

Every new positive debt requires Nom or Société du débiteur. A correctly matched update may omit these identity fields. Every positive debt row requires a usable Téléphone or E-mail. A correctly matched credit note may omit identity and contact details. For a balance or status update, repeat the contact details required by the flow. Identity fields may remain blank when the reference unambiguously matches an existing debt.

​
Understand amounts and credit notes

A negative row needs its own Internal ID plus a target Invoice reference or fallback Debtor reference. Internal ID is the credit note’s stable identity. A negative row without it is rejected. Debtor matching also considers workflow, creditor, and currency.

​
Understand statuses

Technical equivalents active, paid, failed, archived, settled, and manual_takeover are accepted.

​
Distinguish rejected, empty, and partially skipped files

A file rejected before application changes no debt. Depending on the configured validation path, a file with no data rows can be rejected before application or reach synchronization. If it is applied in full_sync, it represents an empty active scope and can settle every active debt. In status_sync, it applies no update. In full_sync, the authoritative perimeter contains the rows retained for synchronization. An existing reference found only on a skipped row can therefore be considered missing.
Never use an empty file as a closure command. Treat every skipped row as a blocking incident before activation.

​
Debt grouping

GetBill can group active debts for one debtor when they share the same phone or fallback Référence débiteur, workflow, GetBill company, and creditor. Paid, resolved, partial, archived, or independently scheduled debts do not join a new group.

Understand the examples

Review the J1/J2 examples matching your profile.

Review every field

Check required, conditional, and optional fields.