ESEN
Sales and support 442 138 8102 Request a demo
For customs brokers and foreign trade

From the customer file to your ERP file, without chasing paperwork.

Fisher Platform brings together in one place the importer's digital file, letters that fill themselves in, a portal where your customer uploads and signs what is missing and an inbox that reads each customer's invoices, in whatever format they send, and delivers them ready for your ERP.

Book a demo Watch the video
  • A checklist built from the profile table
  • PDF, Excel and CFDI in the same flow
  • A new customer is a mapping, not a development project
Customer onboarding · OctoberIllustrative view
Autopartes Delta · legal entity26 of 33 requirements · commission letter signed
Integrated
Farmacéutica del PacíficoTax certificate expires in 12 days · upload link sent
In validation
New supplier · cross-checkThe RFC appears on the SAT's 69-B list
Review
Inbox: 6 different invoice formats → 1 file for the ERP
A brokerage's day to day

Six things that are still done by hand

None is hard. All together they eat the week of the onboarding, classification and invoicing team.

Chasing documents by email

Articles of incorporation, power of attorney, tax certificate, compliance opinion… requested one by one and received in five different emails.

Validity dates nobody watches

The tax status certificate expires after 60 days and the engagement letter after a year. You find out when an operation is already stopped.

Letters copied and pasted

The commission letter and the engagement letter are redone in Word for each customer, with the risk of leaving the previous customer's RFC.

Cross-checking by eye

Is the address on the certificate the same as on the proof of address? Is the RFC on the 69-B list? Is the representative the one in the power of attorney? It is checked by eye, when it is checked.

Each customer, one invoice format

One sends a PDF, another a formatted Excel, another the CFDI. Someone types the line items one by one into the brokerage's system.

"What are we missing?"

The customer calls to find out what is missing and the account executive has to open shared folders to answer.

How it all fits together

Five pieces that talk to each other

Each one works on its own, but together they close the complete cycle of a brokerage's customer.

1

Profile table

Type of person, tax regime, line of business, customs offices and broker licenses. Which documents are requested depends on these data.

2

Case file

The checklist builds itself, with validity dates, cross-check rules, ruling and report.

3

Letters

Commission letter, engagement letter and onboarding form come from templates with the customer's data.

4

Customer portal

The customer sees what is missing, uploads it, downloads their letters and returns the signed ones.

5

Document inbox

Their invoices, in whatever format they send, are read and come out in your ERP's file.

In one minute

See it working

A tour of the case file, the letters, the portal and the inbox, with fictitious demo data.

Digital case file

The customer file knows what is missing, what expires and what doesn't add up

  • Conditional checklist: if the customer only imports, they are not asked for export letters; if their proof of address is not in their name, the lease agreement is also requested.
  • Validity dates and traffic light per document: the tax certificate at 60 days, the compliance opinion, the engagement letter.
  • Smart cascading capture: it reads the QR, then patterns, then local OCR and, only if needed, an AI model on the text.
  • Statuses defined on screen: prospect, requirements pending, in validation, in signing, integrated or rejected.
admin/expedientes/record/7
An importer's file. On the left, what has to be gathered and its status; on the right, the profile table that decides what is requested.
Cross-check and ruling

Cross-check rules review what used to be reviewed by eye

  • That the RFC on the certificate is the customer's, that the address matches the proof of address, that the representative is the one in the power of attorney.
  • That the RFC is not on the SAT's 69-B list and that the line of business is not in a sector restricted by your policy.
  • File templates for legal entities, individuals and domestic suppliers, with 44 starting cross-check rules, all editable.
  • A file report ready for the archive and for the audit.
admin/expedientes/rules
Templates by customer type.
File report.
Foreign trade

The customs vertical, built on top of the file

  • Administrable catalogs of broker licenses, customs offices and sectors with policy (accept, review or reject).
  • The SAT 69-B list is imported and cross-checked on its own against customers' and suppliers' RFCs, every night.
  • The customer is born as a prospect when their file is opened and stops being one when it is integrated.
  • Foreign trade tab in the customer record, with their customs offices, broker licenses and contact roles: who gets invoiced and who gets charged.
admin/clients/client/8
Customer record. Balance, credit and file progress at a glance, and contacts with their role.
Catalogs of broker licenses, customs offices and sectors.
69-B list imported and cross-checked.
Document templates

Your commission letter, filled in with each customer's data

  • Upload your template in Word, Excel or HTML with markers such as [razon_social] or [aduanas]. The legal text is yours; the system only fills it in.
  • Formats when filling in: uppercase, dates in words, amounts with their currency, quantities in words, tables that repeat for each customs office.
  • Each document has its own cycle: generated, sent, signed and verified, with its PDF version.
  • It is generated from the file's own requirement, and the signed copy comes back to the same place.
admin/doc_templates/template/1
Commission letter. Each marker in the template is filled with a datum from the customer, the profile or the brokerage.
Generated documents and their status.

Seven starting letters

Commission, 59-V, rule 1.4.14, beneficial owner, OEA, import and export engagement letters, plus the onboarding form. No legal text: you upload the official one.

Customer portal

Your customer sees what is missing and resolves it on their own

The same file, seen from the customer's side: no calls to ask and no shared folders.

clients/expedientes/expediente/7
"What we are missing." The customer sees their progress and uploads each document in its requirement.
  • Uploads in its requirementWhat they deliver is left as "delivered", never approved: the brokerage decides that.
  • Their documentsLetters to sign, what they have already delivered, their contracts and the PDF of their invoices, on one screen.
  • Their companyA change of company name or RFC comes in as a request that a manager approves.
  • No user account, if they preferAn upload link with only what is missing, with optional PIN and expiry.
Customer documents.
Foreign trade, view only.
Document inbox

Each customer sends their invoice however they want. Your ERP always receives the same thing.

The inbox collects, recognizes, reads and normalizes your customers' invoices, and delivers them in the file your billing system already knows how to swallow.

1

Collects

From a watched folder or by API, with a fingerprint so the same document is not processed twice.

2

Recognizes

It decides the type by its content and by keywords; anything doubtful goes to quarantine.

3

Reads

PDF, spreadsheet or CFDI: header and all line items, with their confidence.

4

Normalizes

Tariff code, NICO, unit, country and weights in a single schema, wherever it comes from.

5

Delivers

Your ERP's file, by folder, SFTP, S3 or webhook, and everything by API.

Designer

A new customer is a mapping, not a development project

  • A fixed, visible path: source, sample, reading, data, destination and activate. Each node is configured in its own panel.
  • With a sample document, the live reading shows what comes out of each field as you adjust.
  • A wizard to set up a new customer or format, step by step.
admin/docinbox/designer/9
Designer. The path of a customer format, node by node.
Data read

Each datum, with its source and its confidence

  • Invoice number, supplier, customs declaration, customs agent and all line items, with their tariff code, quantity, value and weights.
  • A badly read datum is corrected on the screen itself, before it travels to the ERP.
  • A cross-cutting screen with everything all jobs have read, filterable and exportable.
admin/docinbox/item/7
Extracted data, from all jobs.
Output format, as configuration.
Pilot under way. Today the inbox processes, for a customs brokerage, the invoices of multinational manufacturers in the automotive, medical equipment, elevator, industrial, bearings and home appliance sectors: six formats that look nothing alike —PDF with a table, PDF with the item on two lines, PDF with a customs summary, an already-mapped Excel, a formatted Excel and CFDI with the foreign trade complement— and that come out in a single file for its billing system. The screenshots use fictitious "DEMO" customers.
Benefits

What each person gains

Onboarding team

Onboards in days, not weeks
  • The right checklist for each customer, without thinking about it.
  • The customer uploads their own; you only validate.
  • Letters ready to sign in one click.

Classification and invoicing

Stops typing line items
  • Invoices in any format, read and normalized.
  • The ERP file, generated and delivered.
  • Anything doubtful goes to review, never silently.

Management and compliance

Evidence in order
  • Validity dates and traffic light for all customers.
  • Cross-check with the 69-B list and sector policy.
  • Report per file for the audit.

These modules are part of Fisher Platform: they share customers, contacts, document storage, email, role permissions and API with the rest of the platform, and with Bastino, the copilot that answers "what is missing from this customer's file?"

Next step

How we get started

1

Demo

The complete cycle of a customer: from the profile table to the invoice in your ERP's file.

2

Your formats

You send us a sample of your customers' invoices and your ERP's specification.

3

Mapping and templates

We configure your files, your letters and one inbox job per format.

4

Operation

Your first customers and your first invoices, supported by our team.

Frequently asked questions

What we are usually asked

Is each new customer in the inbox a development project?

No. A new customer is a mapping: you upload a sample document, say on screen which data is which and activate it. Your ERP's output format is also configuration, not code.

Which formats does the inbox read?

Invoices in PDF with an item table, spreadsheets —already-mapped dumps or formatted invoices— and CFDI in XML with the foreign trade complement. It first reads the QR code and the document structure; OCR and artificial intelligence only come in when needed, and it can use a model of your own inside your network.

Does my customer need a user account to send their documents?

Not necessarily. They can sign in to their portal, or receive an upload link that only lets them upload what is missing, with an optional PIN and expiry date.

Can I use my own letters?

Yes, and it is the recommended way. The starting templates carry no legal text: you upload your official template in Word, mark where each datum goes and the system fills it in.

Where are the documents kept?

In the storage you choose: your own server, Amazon S3, Cloudflare R2, SFTP, OneDrive or Google Drive, with encryption at rest per destination if you enable it. Downloads always respect the permissions of whoever requests them.

Does it connect to my current ERP?

Yes. The inbox generates the file in the exact format your ERP expects —separator, encoding, line ending, records and fields— and leaves it in a folder, over SFTP, in S3 or by webhook. Everything that is read is also available through the REST API.

Book a demo

Bring us one of your customers' invoices and watch it come out in your ERP's file.

Fisher Networks ventas@fishernetworks.net 442 138 8102
Send an email
About the screenshots and the data

The screenshots are from a demo environment with fictitious companies and people. The inbox's customers appear as "DEMO A" to "DEMO F" and the processed invoice is made up; no data corresponds to a real customer. The pilot is described without naming the participating companies. References to the list in article 69-B of the Federal Tax Code and to procedures before the SAT are informational and do not constitute legal advice.

View plans