Fifty vendors take payments. Treasury has to reconcile every one of them.

Your settlement files, BAI2 bank deposits, and GL postings land in the same warehouse keyed to merchant ID, batch, and date, so deposit-to-GL matching becomes one exception queue instead of a spreadsheet per processor. The BAI2 format has no merchant ID field, so the ID arrives inside the free text or the bank reference, formatted differently at each bank; Synopsis learns each bank's string once, so deposits arrive keyed to merchant ID instead of arriving as a research project. Matching runs at the settlement batch level, batch by batch and fee by fee. BAI2 today, camt.053 when your bank cuts over. Synopsis brings the records together for analysis; it doesn't replace your systems of record.

Reconciliation runs on settlement summaries, batch totals, fees, and deposit records rather than cardholder data, so the warehouse typically sits outside the cardholder data environment. Your QSA makes the scoping call; the same merchant ID inventory gives them the systems list they ask for first.

No. Synopsis reads BAI2 today and camt.053 once a bank cuts over, and it reads both at the same time while some of your banks have moved and others have not. Neither format carries a merchant ID field, so the ID still arrives inside free text or a bank reference, and the pattern learned for that bank carries across the change. Matching still runs at the settlement batch level.

Yes. Elavon settlement files and bank BAI2 deposit records land in one warehouse keyed to the same merchant ID and settlement date, so unmatched deposits surface in one query. The same holds for Stripe, TouchNet, Kyriba, Workday, and the other vendor systems taking payments across your campuses.

Usually, yes. The AI builds the connector from an export or an API, and a new system is typically flowing in days. If it can produce a file, it is a candidate.

Your first connected systems are answering questions in about 48 hours, and a full rollout lands in days, not a multi-quarter data project.

No. We configure your warehouse with you and connect the systems you already run; your team just asks questions in plain English. Nobody has to write SQL or babysit pipelines unless they want to.

No. Your systems of record — ERP, CRM, accounting, and the rest — stay exactly where they are. Synopsis sits on top and joins them into one place you can query, so you report across everything instead of exporting from each tool.

Your data stays in your own warehouse — we don't keep a copy. Access is governed per user and every query is audit-logged. Synopsis is SOC 2 Type II, and you can review our live security posture in the Trust Center.

BI tools chart data that something else already had to clean and join. Synopsis does that upstream work — connecting your systems, resolving entities, and enforcing your metric definitions — then answers in plain English, builds the dashboards, and traces every number back to its source.