Pārbaudīt uzņēmuma un tā partneru nodokļu parādu

Kad izmantot

The weekly scheduled check of the company's own tax debt and of the partners on the watch list. Not for a one-off deep check before signing a new customer — use sales.check-new-customer, which runs this playbook's S2–S3 once for the candidate and adds more checks. Not for the company's own VAT filing — that is money.vat-return-lv; this playbook only reads what is owed, it never files or pays. Registry-only watching without the debt angle is company.registry-watch.

Pirms sāc

• The watch list exists and each row has the partner's LV registration number — a name alone is not searchable.
• The company's own VID portal access (or the accountant's) is available for the exact own-debt figure.
• Last week's log is at hand; "new" means an amount that was not there, or grew.

Ko izpilde pieprasa1

Ceļš7 soļi

1. S1

   Refresh the watch listaģents

   Pull the active customers and critical suppliers from the modules, drop ones with no open business, add new ones.

   Izdarīts, kad the list for this run shows each party with its registration number and why it is watched.

2. S2

   Check the company's own debtaģents

   Look up the company by its registration number in the VID public debtor search; for the itemised figure open the VID portal and read the per-tax breakdown.

   Izdarīts, kad this week's own total, per tax and as-of date are written in the log, read back from the source, not from memory.

   ⛔ The public search can lag behind the portal — never quote the public figure as the company's current debt.

3. S3

   Check every partner on the listaģents

   For each partner: VID public debtor search (debt yes/no, amount, date) and the lv-registrs module for status — active, reorganisation, insolvency proceedings, liquidation.

   Izdarīts, kad one log row per partner with the result and the check date.

   ⛔ "Checked, nothing" without the source and date is not a row.

4. S4

   Diff against last weekaģents

   Compare each row with the previous run. Flag: any debt that appeared, any amount that grew, any status change (insolvency, liquidation).

   Izdarīts, kad every difference is marked "new" or "grown" with both figures.

5. S5

   Decide on findingsīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S5 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Present the flagged rows with the partner's exposure (open invoices, pending deliveries). The owner decides per partner: nothing, demand payment, hold shipments, demand prepayment, or start sales.follow-up-offer / ops.contract-renewal-watch action.

   Izdarīts, kad each flagged row has a named decision and decider.

6. S6

   Record the decisionsaģents

   Create a task for each decided action with its due date and link it to the partner's record.

   Izdarīts, kad every decision from S5 has a task or an explicit "no action" note.

7. S7

   Reportaģents

   Send the owner the weekly three-line summary: own debt unchanged/grown, partners flagged, decisions taken.

   Izdarīts, kad the summary is sent and the log is stored for the next run's diff.

Pārbaudes — kā zinām, ka izdevās

• Every watched party has a log row with a source and a date from this run — no row older than 7 days.
• The company's own figure comes from the VID portal breakdown, and the public-search figure is noted next to it.
• Every "new" or "grown" flag from S4 has a decision in S5 and a task or note in S6.
• The watch list count matches the active customer/supplier lists — nothing was skipped silently.

Ja noiet greizi

Ko atstāj katrs solis

1. S1the list for this run shows each party with its registration number and why it is watched.
2. S2this week's own total, per tax and as-of date are written in the log, read back from the source, not from memory.
3. S3one log row per partner with the result and the check date.
4. S4every difference is marked "new" or "grown" with both figures.
5. S5each flagged row has a named decision and decider.
6. S6every decision from S5 has a task or an explicit "no action" note.
7. S7the summary is sent and the log is stored for the next run's diff.

Ko saglabāt

This week's full log (party, registration number, result, source, date) · the diff against last week · the owner's decisions with names · the tasks created · the sent summary. A run is trustworthy when a person who was not present can open the log and see what was known on which date and from which source.

Kā šī procedūra uzlabojas

After every 8 runs ask: did any debt found here cause a loss that an earlier find would have prevented, and which step would have had to change? How many false escalations did S4 produce — should the "grown" threshold be an amount, not any change? Did the watch list drift? A new version names the step it changes in its change note, per management.improve-playbook.