Supplier Quickstart¶
You were invited to deliver data to a project on Expecto. This is the whole job in five minutes: upload your files, read the feedback, fix anything that's flagged, and resubmit. You do not need to understand how the receiving side is configured.
What you need
- The invitation link (or login) you received by email.
- Your data file(s) in the format agreed with the receiver — usually a CSV or Excel export from your system.
Step 1 — Sign in¶
Open the link from your invitation and sign in. You land directly on a submission view scoped to exactly the delivery you were invited for — you will not see anyone else's projects or configuration.
Step 2 — Start a delivery and upload your files¶
Create a new delivery (a session) for the current period and upload a file for each requested role. A typical FIBU delivery, for example, asks for two files — a bookings file and a balances file; upload each against its labelled slot.
Once your files are in, the platform runs them through its pipeline automatically:
uploaded → parsed → transformed → validated
You don't trigger these stages by hand — they run for you.
Step 3 — Read the result¶
When processing finishes, the session shows a health indicator and a list of any violations:
- Green / no violations — your data passed. You're done; the receiver takes it from here.
- Violations listed — each one points at the rows and the rule that failed, with a message explaining what's wrong (for example, "Konto must be 6 digits").
Errors block the delivery; warnings are surfaced for awareness but may not block.
Step 4 — Fix and resubmit¶
If something is flagged:
- Read the violation message — it names the field and the expectation.
- Fix the data in your source file.
- Upload the corrected file to the same session and let it re-run.
Repeat until the delivery is clean. There's no email round-trip — you get the same validation the receiver does, immediately.
Step 5 — Done¶
Once your delivery passes and the receiver approves it, your job is complete. You can review your past sessions any time from the same view.
If a term is unclear¶
Validation messages sometimes mention rules, entities, or contracts. You don't need them to submit, but if you're curious, the Concepts section explains the vocabulary — start with Session lifecycle.