Counterparty screening and compliance, on by default

Most finance teams treat compliance as a thing that happens at the edges of the calendar: a scramble before a filing deadline, an awkward conversation when a payment turns out to have gone to the wrong sort of counterparty, an audit request that sends everyone digging through email. The work is real, but it tends to be reactive — done when something forces it, not continuously. FINMOZG is built on the opposite assumption. Counterparty screening, sanctions checks and deadline tracking run by default, in the background, the moment the conditions that trigger them appear.

The principle underneath all of it is simple and deliberate: the system surfaces, it does not silently clear or block. When a counterparty matches a watchlist, the platform does not quietly let the transaction through, and it does not quietly stop your business either. It holds the case, gathers the evidence, and puts it in front of a person to decide. Compliance is a place where automation earns its keep by being thorough and visible, not by making decisions on your behalf.

Compliance that runs by default, not at year-end

The reason compliance so often becomes a fire drill is that it is bolted onto a process that was not designed to carry it. Bookkeeping happens one way; screening and deadlines are remembered separately, by people, when they can. FINMOZG folds compliance into the same continuous flow that handles the books. The Compliance Agent watches for the events that should trigger a check — a new counterparty, an approaching deadline, a change in a sanctions list — and acts on them as they occur rather than waiting for a quarter to close.

That continuity matters for two reasons. First, problems are cheaper to handle early: a flagged counterparty caught before the first payment is a question, not an incident. Second, continuous operation produces a record. Because screening and deadline tracking happen as deterministic, logged steps, you can show a bank or an auditor not just that you are compliant today but that the controls have been running all along. That evidence trail is described in detail in how an immutable audit trail protects financial integrity.

Screening a counterparty

The natural moment to screen a counterparty is when it first enters your world — a new supplier, a new customer, a new party on an invoice or a payment. At that point FINMOZG runs a know-your-business check: it captures who the counterparty is, and screens it against the watchlists and sanctions lists relevant to your jurisdiction. This is a deterministic engine, not a guess — the same inputs produce the same checks, and the result is recorded with the evidence behind it.

• Triggered when a party is added. Screening fires when a new counterparty appears, so a party is assessed before it becomes part of your transactions rather than after the money has moved.
• Watchlist and sanctions lists. The counterparty is checked against the relevant lists, and any match is captured as a potential flag rather than a verdict.
• A clear result is recorded too. When there is no match, that clear result is logged with a timestamp, so you can demonstrate that a check was actually performed, not assumed.
• Evidence travels with the result. Whatever the outcome, the match details and the list consulted are attached, so a reviewer or an auditor can see why the system reached its conclusion.

The point is to make the check routine and inescapable. You do not have to remember to screen a new supplier; the act of adding it is what triggers the screen.

When something is flagged

A flag is the moment where the design philosophy shows. A watchlist or sanctions match does not auto-block the counterparty and freeze your operations, and it certainly does not get cleared silently so the transaction can proceed. Instead the case is held for human review. The Compliance Agent assembles what a person needs to make the call: the match, the list it came from, the strength of the match, and a recommendation.

• Held, not blocked. The counterparty is paused pending a decision. Nothing transacts with it silently while the flag is open.
• Held, not cleared. Equally, the system does not dismiss the match on its own. A human decides whether it is a true hit or a false positive.
• Evidence in front of the reviewer. The match and its source are attached, so the decision is made on facts rather than on a yes-or-no signal.
• The decision is logged. Whatever the reviewer chooses — proceed, request more information, or decline — that choice, who made it and why is written to the record.

This is the same human-approval boundary that governs the rest of the platform. Just as tax submissions, payments and payroll release always require a person to sign off, a compliance flag always requires a person to resolve. The agents prepare the decision; they do not make it.

Re-screening as the world changes

Screening a counterparty once is not enough, because the lists themselves are not static. A party that was clear last quarter may appear on a sanctions list this quarter, and you would never know if you only ever checked at onboarding. FINMOZG re-screens counterparties as the lists change, so a newly added name is caught against parties you already work with — not just against parties you are adding for the first time.

• Lists are not permanent. Sanctions and watchlists are updated continuously; a clean result has a shelf life.
• Existing relationships are re-checked. When the lists move, your established counterparties are re-screened, so a new listing surfaces against a party you already pay.
• A new flag follows the same path. If re-screening produces a match, it is held for human review with evidence, exactly as a first-time flag would be.

Re-screening is the difference between a one-time formality and an actual control. It is the reason a party you cleared months ago does not quietly become a liability without anyone noticing.

The compliance calendar

The other half of compliance is deadlines, and this is where the most ordinary failures happen — a return filed late, a contribution missed, a draft started the night before it is due. FINMOZG runs a compliance calendar that turns every filing obligation into a tracked task with a due date and an owner. The Ukrainian obligations — ПДВ, ЄСВ, ПДФО and військовий збір — become scheduled work rather than things to remember.

• Every deadline is a task. Each obligation in your country pack is tracked with its due date, so nothing depends on someone holding the calendar in their head.
• Drafts prepared ahead of time. The relevant agent assembles the return in advance from the books, so the work is ready well before the deadline rather than scrambled at the last minute.
• Human approval before submission. A prepared draft is staged for a person to review and approve. The agent never submits to ДПС on its own — filing is a hard human boundary.
• The whole cycle is recorded. Preparation, review and approval are logged, so the filing history is auditable after the fact.

The mechanics of the Ukrainian filing chain — КЕП signing, Медок and СОТА, submission to ДПС — are covered in automating ПДВ and КЕП in Ukraine. The calendar is what makes sure those mechanics start early enough to be calm rather than frantic.

The Compliance Agent and the Auditor, working together

Screening and the calendar are the work of the Compliance Agent, but it does not work alone. The Auditor sits alongside it, continuously checking the integrity of the record the Compliance Agent produces. Where the Compliance Agent asks "should we transact with this party, and is this deadline handled?", the Auditor asks "is the evidence consistent, and does the trail hold together?". Together they make compliance both proactive and verifiable.

All of this rests on the platform's security model — per-tenant encryption, customer-managed keys and an immutable, hash-chained log — so the compliance record is not just produced but protected. You can read how that works on the security page, and see how the agents are scoped on the agents page.

The honest summary

Compliance automation is easy to oversell. FINMOZG's claim is narrow and concrete: it makes screening and deadline tracking happen by default, it prepares the work ahead of time, and it keeps a human in control of every judgement that carries accountability. A flagged counterparty waits for a person. A return waits for approval. The system's job is to make sure nothing slips through unseen and nothing is decided in silence. If you want to see how this fits your obligations and jurisdiction, you can compare plans on the pricing page or get in touch.