SupplierSift security
Your AP data moves through a visible, controlled path.
See where invoice data moves, how access is scoped, and which decisions remain under human control.
The data path
The source document stays connected to every downstream decision.
SupplierSift processes construction invoices and receipts through a defined custody chain. Each system has a bounded job in that chain.
- 01
Receive
Email, M365, upload, or receipt MMS.
- 02
Store
Source files in R2, structured state in Neon.
- 03
Extract
Google Gemini reads document content for extraction.
- 04
Decide
SupplierSift checks, grounds, routes, and records.
- 05
Write
An authorized person confirms Procore or QBD.
Credentials and links
Connection secrets stay separate from ordinary business records.
SupplierSift keeps infrastructure secrets in Cloudflare Worker secrets. Procore connection tokens use AES-256-GCM envelope encryption before database storage, with the encryption key held outside the database.
- Browser sessions
- Passwordless magic links, secure cookies, and tenant membership checks.
- Procore tokens
- Encrypted envelopes opened only with the Worker-held key.
- Review links
- Scoped to the assigned invoice, receipt, project, or queue authority.
- Receipt links
- HMAC-signed, tenant-scoped, and time-limited source-document links.
Example permission boundary
Invoice admin
View, resolve, and edit invoices. No push or delete permission.
Billing admin
Manage billing and read invoices.
Member
Read-only invoice, receipt, and worker access.
Tenant access
Restricted members get only the routes their role permits.
Owners and administrators manage their company. Invited members use resource-level permissions for invoices, receipts, workers, settings, connections, billing, and team management. Unmapped tenant routes deny restricted members by default.
Service boundaries
Each external provider handles one part of the workflow.
SupplierSift does not hide the vendors behind the product. The current architecture uses the following services.
Cloudflare
Workers process requests and email; R2 stores source documents.
Neon
PostgreSQL stores structured business, workflow, and audit state.
Google Gemini
Receives document content for invoice and receipt extraction tasks.
Procore
Supplies permitted project data and receives confirmed invoice writes.
Conductor
Bridges confirmed reads and writes to QuickBooks Desktop.
Twilio
Carries receipt MMS and Ask Worker messages.
No silent accounting decisions
Uncertainty becomes a blocker a person can inspect.
Extraction can be automatic. Math failures, ambiguous matches, missing destination identities, approval, and write confirmation remain visible states in the workflow.
Write controls
- Auto-Fix commits only grounded fields when configured.
- Vendor, PM, and team sends require an operator action.
- Human approval clears the payable.
- Procore and QBD writes require separate confirmation.
- History and audit records preserve the action trail.
Certification posture
This page makes no certification claim.
SupplierSift does not currently claim SOC 2, ISO 27001, SSO, SAML, or another unheld certification or enterprise identity feature. Security statements here describe the shipped architecture and controls.
See your own invoice
Forward one real supplier invoice.
SupplierSift reads it, checks the math, and emails you a secure link to the result in your dashboard.
try@suppliersift.com Forward an invoice a supplier already emailed you.
Open an invoice a supplier sent you and hit Forward. Keep the original email intact so SupplierSift can verify who sent it.