Your factoring company, automated

Your firm connects its accounts through Open Finance, the official scheme that lets a bank share your own data with whoever you authorise. From there Capitalis reads balances, inflows, outflows and every single transaction in real time. This is not a spreadsheet exported from internet banking at the end of the day. It is the bank's own position, inside the screen where you decide credit.

Reconciliation matches each statement line against its entry. What does not match stays visible as what it is, a difference to explain, instead of disappearing inside a total that happens to add up.

• Read access, never movement. The Open Finance consent authorises reading balances and statements. The platform does not transfer, does not pay and does not take money out of your account, and the client revokes access whenever they want, in their own bank's app.
• A credit card is not cash. The service that brings in the bank data returns the current account and the card in the same list, under the same label. On a card that number is the open bill, which is a debt. Adding it all up would make an R$ 8,000 debt show as a positive balance on a screen whose whole purpose is deciding credit. Each account carries its nature and totals are added up in separate groups.
• An authorised purchase is not money that has left. Pending transactions go to a block of their own and stay out of the period cash.
• Money in is money in, money out is money out. The platform standardises the sign of every amount, whatever convention each bank uses on its side. Without that fix, a card purchase would land in the analysis as revenue.

The slip is issued from inside the invoice batch itself. You pick the receivables and Capitalis registers the charge with the partner issuing bank. The slip comes back with the real payment line, the one a teller and a banking app can actually read. The amount charged is the balance still outstanding, not the full face value. If the debtor already paid 1,500 of a 5,000 receivable, the slip comes out at 3,500.

Money never passes through Capitalis. What gets paid is your firm's own account inside the issuing bank, chosen on screen, and when it changes the platform asks for confirmation showing which account it is moving from and to. Slips and Pix credit that same account. The platform instructs the bank, it never holds your money.

• A receivable is only settled once the bank confirms it. The payment notice arrives signed, and even signed it is treated as an alert, not as truth. Before settling anything, the platform asks the bank whether the money actually came in. A forged notice settles nothing.
• One payment credits once. Three barriers hold a repeated notice. The platform recognises a notice it has already seen, locks the record while it updates, and refuses to settle what is already settled. The amount received is spread across the covered receivables, up to each one open balance. A receivable already cleared another way is not paid again.
• Pix with a due date, single use or reusable. QR codes come from the same connection and credit the same account of your firm.
• Cancelling means cancelling at the bank first. Only then does the slip show as cancelled here. Marking it cancelled without telling the bank would leave it still payable out there.
• Flat fee per event, never a percentage. Ticket sizes in this industry are large. One percent of a 10,000 receivable is 100 on every settlement, which eats your firm margin. A provider that charges a percentage is ruled out here.

You build the cadence counting days from the due date. A reminder three days before, WhatsApp on day one of arrears, SMS on day seven, e-mail on day fifteen. From there the system fires on its own, inside the limits you configured, start hour, days of the week, a daily message cap and a pause on holidays. The cadence ships switched off. No firm should start chasing its customers automatically just because the software was updated.

When the due step is a conversation, the receivable joins the dialling queue instead of becoming another SMS, and the call goes out through the in-browser dialer, with both sides recorded on separate channels.

• A filing that exists at the bureau, not just on screen. Filing a debt records it at the credit bureau before the platform writes anything here. If the bureau refuses, the screen shows an error and nothing is stored. A filing that exists only in here is worse than none, because the firm believes the debtor is restricted while their credit stays clean.
• The waiting period the law grants the debtor lives in the system, not just in a manual. The record goes in first as a notification. Those are the ten days the bureau must give the debtor before filing. Only then does it become a filing. When the receivable is paid, the platform asks the bureau to delete it, because clearing the record within five business days of payment is the creditor's duty. If the bureau fails, the local clearing does not happen either, so the screen never says resolved while the debtor is still restricted.legal basisart. 43 §2 and §3 of the Brazilian Consumer Code · STJ Precedent 359
• Notary protest without leaving the screen. The request goes to the protest registry before the platform stores anything, and protocol, notary office and status flow back into the receivable, from filing to summons, protest, payment or withdrawal. Clearing files the withdrawal through the same channel.
• One button re-reads the status at the bureau and at the notary. The cycle runs out there, not here. A screen that never re-reads grows old saying filed forever.
• No contact, no promise. A debtor with no e-mail does not get an e-mail step. The platform switches to a channel that does exist, and when none does the row is flagged and the button switched off, with the reason in plain sight.

Capitão IA is the platform assistant. You ask how much is overdue, which debtor concentrates risk, how cash looks over the coming weeks, and the answer comes from your own live data. You can dictate the question, and the transcription happens inside your own browser, with no audio leaving the machine and nothing stored.

The artificial intelligence has no access to the database, and that is deliberate. Before anything is asked of it, the platform assembles a summary of your numbers, read-only, already limited to your own firm and to what the person asking is allowed to see. The answer comes only from that summary. An administrator sees the consolidated picture, narrower access gets less, and there is no path by which a well-crafted question reaches another firm data.

• What goes into the summary is declared. Portfolio and open receivables, overdue amounts, the month volume and result, how long each one is late, own revenue over recent months, the top five debtors and clients with their concentration percentages, and a four-week cash flow projection.
• Text coming from outside is treated as suspect. The question and the data go in separated by explicit markers. It is the known defence against someone hiding an instruction inside a piece of text for the AI to obey.technical nameprompt injection mitigation by delimiters
• Every question is recorded. Who asked, when, and the beginning of the text stay in the audit trail, like any sensitive action.
• If it fails, it does not stop. With no artificial intelligence available, the analysis falls back to the local calculation, which always gives the same answer for the same numbers, and the screen says which mode it is in.

Everything the platform does on screen can also be done by another system, through a documented entry point. Each system gets its own access key, with what it may do and a date when it expires. That is how the client's management software, the accountants and any automation your team writes get in.

Capitalis also opens a ready door for artificial intelligence assistants. In practice you connect Claude, Claude Code or Cursor to your own operation and ask in plain language, with the assistant answering from your real data.

• There is no shortcut to the database. Each tool the assistant uses goes through the same door the screen uses, carrying the credential of whoever called it. The assistant sees exactly what that access and that firm allow, under the same isolation as ever.
• Read-only, by decision. Letting an artificial intelligence write into a financial system requires a human to confirm it, so this first version only reads. Whoever needs to write uses the normal entry point, with a key that carries that permission.
• The catalogue is ready. Dashboard, clients, debtors, deals, open receivables, cash flow, month result, entries and the portfolio, revenue, performance and concentration reports.
• A stolen key, on its own, opens nothing. The access key can be bound to the system that uses it. From then on it only works together with a proof that only that system can give.

In Brazil the trade invoice (duplicata) is no longer paper. By law it is born and circulates as an electronic record at a registrar authorised by the Central Bank, and that is where it is noted who bought it and whether any lien exists over it. The classic fraud of the trade, the same invoice assigned to two factoring companies, stops depending on trust once the lookup comes before the money.

In Capitalis the lien lookup is part of the batch flow. Before approval, the platform checks with the registrar whether the invoice is already assigned or encumbered, shows the result on screen and can block the purchase of an encumbered invoice. After the purchase, the assignment is registered through the same channel, with a protocol flowing back into the deal. The duty to register remains your firm's. The platform is the tool to meet it without leaving the screen.

• Lookup first, money later. The lookup result is stored in the deal, with date and protocol, and approval only proceeds after it.
• An encumbered invoice blocks the purchase, if you want it to. The block is a switch your firm controls. It ships off, so the criterion is yours, not the system's.
• Registration with confirmation. The assignment only shows as registered here after the registrar confirms it, never before.