Remitian

A note on placement before anything else: Remitian is not a document tool and does not belong with the extraction and delivery products it is listed beside. It handles tax payments. It sits in this category for want of a better home, because the moment it addresses, getting the money to the revenue agency after the return is done, falls inside the same span from client documents to filed return that everything else here covers.

The job is one most firms currently do by hand across a dozen websites. Payments are scheduled in a single queue with date, amount, client and jurisdiction, validated against that jurisdiction's rules and against routing and account numbers, submitted through banking infrastructure to the correct revenue agency, and confirmed with a reference number and a proof document. Deadlines are tracked and reminders fire. Coverage spans federal, state and local in the United States and provincial in Canada, with the interface showing NY, TX, CA, FL, Ontario and Quebec, and payment types including corporate, payroll and estimated tax. The audit side is the part a firm should care about most: an append-only log where every action is timestamped and non-editable, cryptographic integrity on the log, and exportable CSV or PDF reports built to satisfy an outside auditor.

For a firm that only ever pays through EFTPS and one state portal, this solves nothing worth paying for. The case appears when a practice is making payments for clients across ten or fifteen jurisdictions on different calendars, each with its own login, its own confirmation format and its own idea of what proof of payment looks like. The reconstruction problem when a client asks in November whether the June estimate went through is the thing being sold.

The evidence is thin in the ways that matter. Fourteen or so firms and platforms are cited as customers, including Xero and Zenbooks, which is a very small base for something handling client money. No price is published in any form, so there is no way to tell whether this is a per-payment fee, a platform subscription or a percentage. The site does not name the banking partner, does not state whether Remitian holds money transmitter licences or moves funds through a partner bank, does not list which state portals are actually connected as against merely supported in principle, and does not say where the company is based or when it was founded. Those are not optional details for a payments company, and a firm should require all of them in writing before routing a client's estimated payment through it.

What is published on security is better than most: SOC 2 Type II with annual third-party audits, PCI DSS Level 1, GDPR compliance and ISO 27001 in progress, TLS 1.3 and AES-256, mandatory MFA, role-based access, annual penetration testing, daily vulnerability scanning, a bug bounty programme and seven-year record retention. A trust portal exists at trust.remitian.com.

There is no comparable product in this directory, so the honest comparison is with what a firm does today, which is state portals and a spreadsheet. One to watch stays. The security posture is unusually complete and the problem is genuine, but a payments platform with fourteen named customers, no published pricing, no disclosed banking partner and no licensing statement is not something to move a season of client payments onto yet.