Client setup

Connect this customer's ERP, map its fields, and manage the private R2 evidence vault.

ERP connections0customer-specific

Mapped fields0standard audit fields

Last sync0records imported

R2 evidence00 B stored

Needs attention0duplicates / file flags

1. ERP connection

Enter what the ERP provider gave youDaily Audit stores credentials encrypted and never displays them again.

Tell us where one type of data livesCreate separate endpoints for sales, purchases, stock, bank data, or payments.

Connect ERP fields to Daily Audit fieldsExample: invoice_total → Net sales. Required fields reject incomplete records.

ERP field path	Daily Audit field	Type	Required

Connect securelyHTTPS only; private/internal addresses are blocked.

Preserve the sourceEvery API response is hashed and kept in private R2.

StandardiseYour mapping converts each ERP's names into one audit vocabulary.

Validate and syncIncomplete rows are rejected and every run is recorded.

Private

Original files use content-addressed SHA-256 keys. Exact duplicates reuse the stored object; JPEG camera date/GPS is checked when available.

Month

Captures days, actions, configuration, evidence references, and ERP import runs. Originals remain in private R2.

No evidence loaded.

No syncs yet.