FX operation documents, checked at the pace of the desk.
QX receives what the client or the correspondent sends, links every file to the right operation, extracts the fields and cross-checks invoice, bill of lading and import declaration. Your analyst reviews exceptions and approves.
Reply within one business day.
Who it is for
Built for teams that close FX with the documents in hand.
-
Banks
The desk closes operations all day and a team checks invoice, bill of lading and import declaration by hand. QX does the checking and the team handles the exceptions.
-
FX brokers
Imports, exports, services, remittances: each nature of operation needs a different document package. QX builds the package per nature and chases what is missing.
-
FX and cross-border payment fintechs
Client onboarding and the documents of each remittance in the same flow, with a REST API and webhooks to connect your system.
-
FX correspondents
Dozens of clients sending documents by email and WhatsApp. QX chases, checks and keeps the trail your partner bank asks for.
The documents
What QX reads and cross-checks in every operation.
The package changes with the nature of the operation: advance payment, sight payment, an import already cleared. QX checks every file against the package and against the other documents of the same operation.
-
Commercial invoice
Line items add up to the total. Exporter, importer and currency match the FX operation.
-
Proforma invoice
On an advance payment, value and parties checked against the operation. The import declaration becomes a pending item with its own due date.
-
Bill of lading (B/L, AWB, CRT)
Shipper, consignee, weight and shipment date checked against the invoice and linked to the right operation.
-
DI and DUIMP
Value, importer and date checked against the invoice and against the amount closed in the FX contract.
-
Articles of incorporation and power of attorney
Company name, tax ID, partners and the signing powers of whoever signs, extracted and checked in the client's file.
-
Partner ID and proof of address
Same tax ID and same person across the onboarding documents. Validity monitored, renewal requested before expiry.
How it works
From the client's email to the analyst's approval.
-
One package per nature
Advance payment, sight, term, services: each nature becomes a template with the documents, fields and validations your compliance requires. Built once with the desk.
-
The document arrives and finds its operation
The client or the correspondent forwards the email, sends by API, drops it in a Google Drive, Dropbox or OneDrive folder, or replies in a form that corrects itself live, no account needed. QX classifies every attachment and links it to the right operation by name, tax ID and amount, even when the document arrives before or after the deal is closed.
-
QX checks, the analyst approves
Invoice total, bill of lading weight, import declaration value against the FX amount. The fields come out extracted and validated, ready for review. Whatever does not match becomes an exception, and whatever falls due later is chased until it arrives.
Why QX
Checking at the pace of the desk, with proof of everything.
-
Built by people who worked the counter
The founders came from Husky, an FX fintech sold to Nomad in 2022, where they opened tens of thousands of accounts on manually checked documents.
-
Items that fall due later
On an advance payment, the import declaration becomes a pending item with its own due date and is chased until it arrives.
-
Clients keep their habits
Documents keep arriving by email, or through the folder and the API the client already uses. Whoever prefers replies in a form tied to their identity that corrects the submission on the spot.
-
Full audit trail
Who sent, who viewed, who approved, when. Exportable for audit and for the regulator.
-
Connected to your FX system
A REST API and webhooks carry the extracted, validated fields into your system; the verified package also goes out by email or to a drive. You can start with no integration, just by forwarding email.
-
Enterprise contract security
SSO/SAML, DPA, pen test under NDA, 99.9% SLA and a dedicated CSM. Encryption in transit and at rest, with role-based access.
Frequently asked questions
What the desk and compliance ask.
-
Does my client need an account to send documents?
No. They forward the email with the attachments or reply through a link tied to their identity. So does the correspondent.
-
How does QX know which operation a document belongs to?
From the extracted data: name, tax ID, amount and date. One email can carry documents for more than one operation, and one operation can receive documents from different emails.
-
What about a document that falls due later, like the import declaration on an advance payment?
It becomes a pending item with its own due date and is chased until it arrives. The analyst sees the list of open items in real time.
-
Do we need to integrate before starting?
No. Forwarding email works on day one, and so does a folder on Google Drive, Dropbox or OneDrive. The integration with your FX system, through the REST API and webhooks, comes when IT has room for it.
-
Who approves the operation?
The bank's analyst, always. QX checks and delivers the validated fields. Approval stays with your team.
-
What security guarantees does a bank get?
On Enterprise: SSO/SAML, DPA, pen test under NDA, 99.9% SLA and a dedicated CSM. Encryption in transit and at rest, with auditable role-based access.
Start with one desk
See QX running on the operations of one of your desks.
Bring the invoice, bill of lading and import declaration of real operations. On the call we show the extraction, the cross-checks and the exception queue.