There's an important technical difference between "automatic debit of the installment on its due date" and what, in expert opinions, has come to be called a checking-account sweep algorithm. The first is predictable. The second captures, in real time, any amount entering the account tied to the credit facility — including instant payments (PIX) and wire transfers from third parties who have nothing to do with the debt — before the company can even use that money for any other purpose.
In this article
The mechanism nobody explains at the branch
This mechanism has shown up, with variations, in more than a third of the technical opinions I've prepared over the past several months — in working-capital operations backed by public credit-support programs (FGI-PEAC) and also in CCBs with real collateral. It's worth explaining, step by step, how it works and why it's far more serious than it looks at first glance.
How the sweep works, in practice
The mechanism follows a technical sequence that repeats, case after case:
The company receives an instant payment from a customer — payment for a sale, a service rendered, of any nature — into the checking account that was, at some point, designated as the operating account tied to the credit contract.
Within seconds, the bank's system identifies the incoming funds and applies a pre-configured capture rule, with no prior notice to the account holder.
The amount is debited and applied to reduce the outstanding balance — not necessarily the month's due installment, but, in some models observed, as a reduction of the total balance, affecting future interest calculations and, under certain contract designs, without even generating a clear, immediate receipt of the write-down for the client.
The money that came in is no longer visible or available for the company to pay a supplier, payroll, or a tax bill due that same day — even when that specific payment had no relation whatsoever to the credit operation.
Is your operating account being swept by the bank?
Request a preliminary technical screening of your business credit contract.
Why "third-party payment" is the most serious part
The distinction between capturing "the debtor's money" and capturing "a third party's incoming payment" isn't a legal subtlety — it's the core of the problem. When a company's customer pays an invoice via instant transfer, those funds have a destination: paying the company's supplier, paying an employee's salary, paying the month's tax bill. If the bank intercepts that flow before the company can redirect it to its operating obligations, the practical effect is this:
The company starts falling behind on obligations it would normally honor — not because it lacks revenue, but because the revenue was captured by a third party — the bank — before reaching the hands of whoever should be managing it.
The delay caused by this capture can, in contracts with a cross-default clause, trigger acceleration of the entire banking debt — a domino effect in which the lender's own conduct creates the default it later uses to accelerate collection.
The company loses financial planning capacity, because it doesn't know, from one day to the next, how much of its cash will actually be available — which makes supplier negotiations, payroll compliance, and even basic tax planning unworkable.
What a forensic audit reviews
When analyzing an operation showing signs of a sweep, the financial forensic audit seeks to reconstruct, statement by statement: the exact timeline of each incoming payment and the interval between the credit and the subsequent debit (in cases observed, that interval ranged from seconds to a few minutes); the origin of the captured funds — whether they came from the company's customers/third parties or from the partners' own capital contributions; whether an installment was past due at the time of capture, or whether it occurred preemptively, with the contract in good standing; and whether the contract expressly disclosed this mechanism clearly enough to constitute informed consent, or whether the clause was generic enough that the client couldn't reasonably foresee the practical reach of the authorization.
The legal grounds involved
This type of mechanism directly strains civil and consumer-law doctrines: Article 884 of the Civil Code (prohibition of unjust enrichment), the duties of disclosure and good faith under Articles 421 and 422 of the Civil Code, and, where a consumer relationship applies, Article 51, IV, of the Consumer Protection Code (nullity of clauses that place the consumer at an excessive disadvantage). In contracts tied to public credit-support programs (Law 14.042/2020, Law 10.931/2004), there's an additional issue: diversion from the assistance purpose of the credit, since a mechanism of this kind hollows out the cash-flow relief the emergency program itself was meant to guarantee the company.
What to do
Working-capital credit exists to give a company operational breathing room. A mechanism that intercepts cash before it can even circulate does exactly the opposite — and, technically, turns a credit operation into a unilateral, silent control over the financial flow of third parties who aren't even party to the contract.
- Read the "linked-account activity" clause carefully. If the language allows "debit of any amount received, at any time," question it and negotiate before signing.
- Avoid concentrating customer receipts in the same account tied to the credit facility, whenever the contract allows a different operating structure.
- Request detailed periodic statements for the captured account, and compare each debit against the contractual installment schedule.
- Document any delay to third parties (suppliers, taxes) that results directly from the bank's preemptive cash capture — this record is decisive in any eventual technical dispute.
This article is part of a series on technical pathologies in business credit operations, based on expert opinions prepared by the author. Individual cases are treated in aggregate and anonymized form, with no identification of the companies or individuals involved.
Frequently asked questions
What is a checking-account "sweep" in banking contracts?
It's a banking system programmed to capture, in real time, any amount entering the account tied to a credit operation — including instant payments (PIX) and wire transfers received from third parties — and automatically apply it to reduce the outstanding balance, often before the account holder can use that money for any other purpose.
Can a bank sweep capture payments received from the company's own customers even when installments are current?
Yes. In audited cases, capture happened systematically and preemptively, with no installment past due at the time — the system treated any cash inflow as collateral reinforcement, regardless of whether the contract was in good standing.
Can this cash capture trigger cross-default from delays on other company obligations?
It can. If the funds that would have paid a supplier, payroll or a tax bill are intercepted by the bank, the company starts falling behind on obligations it would normally honor. In contracts with a cross-default clause, that delay — caused by the lender's own conduct — can trigger acceleration of the entire debt.
How does a financial forensic audit prove the existence of a sweep algorithm?
By reconstructing, statement by statement, the exact timeline of each incoming payment and the interval before the subsequent debit, the origin of the captured funds, whether an installment was past due at the time of capture, and whether the contract described the mechanism clearly enough to constitute informed consent.
Dr. Lincoln Sposito
Specialist in banking audits and financial forensics, combining the statistical rigor of data science with the analysis of banking-system architectures to dismantle predatory charges against SMEs. Learn more about the expert →