Bulk Import (Manual)
EFS publishes a template for each transaction type. Your system produces a matching extract on a cycle, a named person checks it, and it is loaded.
EFS answers instantly — what imported, what failed and why, reported to the person who did the load, who corrects and reloads in the same sitting.
- No code, no credentials, no monitoring
- No retest at every EFS release
- No notice to us before you change your own system
The trade: the ledger is current as of the last load, and somebody has to do the load.
Bulk Import + Interface
Everything above, plus a standing authenticated connection exchanging more frequently, without a person in the loop. It buys currency. It does not replace Bulk Import — you build and keep that too, as the fallback.
Rejections return to a queue, not a person. Nothing is watching unless something is built to watch.
- A named technical owner and backup, permanently
- Monitoring, alerting, and someone who reads the rejection queue
- Retest at every EFS release — twice a year, indefinitely
- Written notice before any change to your system
Everything it asks for exists to replace the person who, on the other route, was already there.