Custom CSV format
A-Cube builds this format for your requirements. To request it, contact A-Cube.
Request a custom CSV format when your export differs from the standard CSV format. A-Cube configures Transfer to accept the layout agreed during onboarding, so you can keep your existing export.
When you need one
- Your ERP uses different column names or date formats.
- You want to keep your existing layout for documents such as Peppol despatch advice (DDT).
- Your systems export different layouts for the same document type.
- You need fixed values, such as a payment method or VAT nature, without repeating them in every row.
What you send A-Cube
- Your column definitions, including each column's meaning and format.
- Files exported by your system for each relevant case: multi-line invoices, credit notes, 0% VAT, and fields that are usually empty.
- The destination.
Use actual exports from your production system. Replace personal data with equivalent test values and tell A-Cube which values you changed.
What you receive
- Column specifications with names, formats, and required values.
- The agreed format configured for your sandbox account.
These file rules also apply: at most 500 data rows per file, UTF-8 encoding, a dot as the decimal separator, and no line breaks inside cells.
From sandbox to production
- Test your exports in sandbox, including the cases above.
- Check upload and document statuses and any violations.
- Correct your export or agree on changes with A-Cube.
- Once the results are correct, ask A-Cube to enable the same format in production.
Changes after go-live
Agree on column changes with A-Cube before sending files in the new layout:
- Describe the columns you want to add, remove, or change.
- Wait for A-Cube to confirm that Transfer accepts the updated layout.
- Start sending files in that layout.
Keep using the old layout until the agreed switch. Transfer ignores unrecognized columns, so their values are omitted from the documents. Renaming or removing a required column can cause a violation.