tiime-upload-justificatifs

name

tiime-upload-justificatifs

description

Use this skill to push the structured YAML fiches produced by `justificatif-describe` into Tiime via a Chromium piloted by Playwright MCP. The fiches live in `$WORKSPACE/receipts/YYYY-MM/`. The skill checks whether each piece already exists in Tiime (auto-created from Revolut sync), attaches the PDF/JPG if missing, and completes the metadata (date, total_incl_tax, vat, label, invoice no., intra-EU VAT number, SIREN). Never validates a piece on first run — stops for human confirmation. Trigger when the user says « upload tiime », « pousse les justificatifs dans Tiime », « complète Tiime avec les YAML ».

Skill — Push YAML fiches into Tiime via Playwright

Overview

Drives the Tiime web interface (apps.tiime.fr) via Playwright MCP to push the metadata of the YAML fiches generated by justificatif-describe into Tiime supplier invoices. The pieces are generally already created in Tiime by the Revolut Business bank sync — the skill therefore acts in enrichment mode rather than pure upload.

When to use

• The user has already run justificatif-describe on the current month (existing YAML in receipts/YYYY-MM/)
• The user wants to fill in / correct the metadata in Tiime from those YAML
• The user has a Chrome session already logged in to Tiime, drivable by Playwright MCP

Do not use to: create a Tiime account, manage mileage expense reports (folder expense/, submenu Notes de frais → Trajets), push DDG client invoices (submenu Facturation, not Dépenses).

Prerequisites

1. Playwright MCP configured and started in the current Claude Code session.
2. Tiime tab open in the Chromium driven by Playwright and logged in to the target company. Check with browser_tabs(action: list).
3. Memory up to date (bootstrap-projet skill run) — to know the audit decisions that may impact the mapping (recat Apple→606800, Otera position, etc.).

Lethal trifecta: this skill manipulates the Tiime session via Playwright. NEVER call an "internal data source" MCP (Asana, M365, Sentry, Slack) in the same session — the hook would then block Playwright. Work 100% local + Playwright.

Tiime navigation — stable landmarks

• Invoice list URL: https://apps.tiime.fr/companies/{companyId}/expense/expense-invoice
• Menu: Dépenses → Factures (selector: getByRole('link', { name: 'Factures' }))
• Dépenses submenus:
  • Factures = B2B supplier invoices (target of this skill)
  • Notes de frais = expenses advanced personally to be reimbursed
  • Trajets = mileage
• Card routing: paid on the EURL Revolut Business card → Factures. Paid on a personal card → Notes de frais.

General procedure

Step 1 — Bootstrap & inventory

1. Run bootstrap-projet if the session is new.
2. List the YAML of the target month folder: ls receipts/YYYY-MM/*.yaml.
3. Read each YAML, count, produce a numeric recap (total_incl_tax / total_excl_tax / vat totals) to present to the user.
4. Identify the blocking pieces (cf. stop rules) — those with a critical alert, code RECEIPT_PARTIAL or corporate_tax status no.

Step 2 — User validation

Present the recap + the at-risk pieces. Wait for explicit validation before touching Playwright. Ask in particular:

• Which pieces with a critical alert should be skipped?
• Which conditional pieces should be uploaded anyway?
• How to handle non-EUR currencies (ECB rate of the day?)?

Step 3 — Playwright connection

browser_tabs(action: list)

If no Tiime tab → stop, ask the user. Otherwise navigate to Dépenses → Factures.

Step 4 — For each YAML (ascending chronological order)

4.1 — Search in Tiime

Does the piece already exist? Strategies:

• Locate the row by date + total_incl_tax amount + merchant in the table (the Revolut transactions auto-create the entry with the bank merchant name).
• Use the search box getByPlaceholder('Rechercher dans mes factures...') if the list is long.

Three cases:

• ✅ Found → open the detail, enrichment mode (cf. 4.2).
• 🆕 Absent but PDF available → upload via the « Importer un document » button (to document on the first case encountered).
• ❌ Absent and PDF absent → report to the user, do not invent.

4.2 — Open the detail

Click the row → a panel opens on the right with:

• Preview of the PDF/JPG (OCR text exposed in region)
• Metadata form
• Voir plus button that exposes the advanced fields (Facture n°, IBAN, SIREN, TVA intracom, Montant en devise)

Always click "Voir plus" to expose the full set of fields.

4.3 — Mapping YAML → Tiime fields

Tiime field	YAML source	Notes
Nom du document	merchant.name or merchant.trade_name	Often pre-filled by Tiime from OCR
Date	document.date	Displayed format « 1 avril 2026 »
Date d'échéance	(case by case)	For an invoice already paid by direct debit: debit date. For an immediate invoice (card): leave empty or copy the document date.
Intitulé	nature.short_description or merchant.name	Pre-filled by Tiime
Montant TTC	amounts.total_incl_tax	spinbutton
Total TVA	sum(amounts.vat[].amount)	spinbutton — for multi-rate, this is indeed the sum
Facture n°	document.number	Optional for cash receipts
Montant en devise	amounts.total_incl_tax if amounts.currency != EUR	To test with ISK / USD
SIREN/SIRET	merchant.siret	For FR suppliers only. If no SIRET but RCS known, the first 9 digits of the SIRET = SIREN
N° TVA intracommunautaire	merchant.vat_number	Format FRXX..., LU..., etc.
IBAN	(not carried by the YAML)	Optional, ignore unless explicitly requested
Label	mapping nature.category → Tiime label	Cf. table below
Commentaire Facture	(free text, always filled, short and concise)	Carry over the notable details from the YAML: discounts, business context, guest no. Style: 1 sentence, 10-15 words max. ⚠️ Distinct from the bank transaction comment, cf. §4.3.bis.
Commentaire transaction bancaire	(free text)	Inline field on /account/transactions, visible directly on the list. To be filled too so the comment appears on the transactions view. Cf. §4.3.bis.

4.3.bis — ⚠️ Two distinct Comment fields in Tiime

Discovery session 2026-05-25 quinquies (Gérard correction): Tiime exposes two separate comment fields, and you must fill BOTH for a complete enrichment.

Field	Location	Selector	Visible from
Commentaire Facture	Invoice detail panel, under "Voir plus"	getByPlaceholder('Ajouter un commentaire') (textarea)	When you open the piece in /expense/expense-invoice
Commentaire transaction bancaire	Inline column on the transactions table	tr.cdk-row input[placeholder="Ajouter un commentaire"]	Directly on the list /account/transactions

Why this duplication? Tiime displays the bank transactions (/account/transactions) with ONE "Commentaire" column for quick triage, independently of the attached Invoice. A single PDF can be linked to several bank transactions (Revolut Business Grow+Dépenses case sharing the same invoice) → each transaction has its own comment.

Rule:

• The Invoice comment is the accounting version (long, CGI references, vat amount, etc.)
• The bank transaction comment is the "list triage" version (short, just to recall what it is)
• For recurring charges (FRAIS BANCAIRES, ASSURANCE, SaaS subscriptions) where Gérard mostly looks at the transactions list, ALWAYS fill the bank transaction comment, otherwise Gérard sees no annotation on his view.

Bank transaction helper pattern:

// On /account/transactions
const inpSetter = Object.getOwnPropertyDescriptor(HTMLInputElement.prototype, 'value').set;
for (const row of document.querySelectorAll('tr.cdk-row')) {
  // Filter by textContent (date + merchant + amount)
  if (!matchTerms.every(m => row.textContent.includes(m))) continue;
  const input = row.querySelector('input[placeholder="Ajouter un commentaire"]');
  if (!input || input.value) continue;  // Skip if already filled
  inpSetter.call(input, commentaire);
  ['input', 'change', 'blur'].forEach(e => input.dispatchEvent(new Event(e, { bubbles: true })));
  await new Promise(r => setTimeout(r, 350));
}

The blur event triggers the Tiime save. Persistence verifiable after a page reload.

Anti-pattern: do NOT confuse the two. Filling only the Invoice comment leaves the transaction column empty, and Gérard sees nothing from his usual view.

4.4 — Mapping category YAML → Tiime Label

nature.category YAML	Target Tiime Label
restauration	RESTAURANT
honoraires	HONORAIRES
materiel-informatique	PETITS MATERIELS ET FOURNITURES (606800) — not LOCATIONS DIVERSES (cf. audit 14/05/2026 on Apple)
deplacement-hebergement	HOTEL
deplacement-stationnement	PARKING
deplacement-transport	(to confirm)
telecom	TELEPHONIE
energie	ENERGIE
fournitures	FOURNITURES BUREAU
mobilier	(fixed asset if > 500 € HT → 2184)
alimentation	(case by case — see accountant AN nourriture position)
logiciel-saas	LOGICIELS
formation	FORMATION

To be enriched as cases are encountered.

4.5 — Mandatory stop rules

Stop and ask if:

• The YAML carries an unresolved severity: critical alert
• The status tax_analysis.corporate_tax_deductibility.status is no (the piece must not be deductible)
• info_to_complete non empty → incomplete piece
• Tiime rejects a value (unknown category, non-standard VAT rate, etc.)
• A YAML field does not clearly map to a Tiime field
• The expected selector is not found (different DOM)
• The Tiime session expires (login screen)

NEVER fabricate a value. Better to stop 10 times than pollute the accounting.

Step 5 — First piece step-by-step

For the first piece of the batch:

1. Present to the user the state of the detail panel (already-filled vs empty fields)
2. List the proposed changes
3. Wait for explicit validation before filling
4. Fill the fields (use browser_fill_form or targeted browser_type)
5. DO NOT save before user confirmation
6. Once confirmed, move to the next ones on autopilot with a stop at every ambiguity

Step 6 — Lifecycle of a piece edit

1. Click the row in the table → detail panel opens on the right with PDF + form
2. Click "Voir plus" to expose all fields
3. Edit the fields: as soon as the 1st change is made, a footer appears with Annuler / Valider
4. Click "Valider" in the footer → commit to the database, footer disappears, other edits still possible
5. Click the cross at the top of the panel (selector ~e2155 / e2137) → closes the panel
6. Click the next piece in the table → new cycle

⚠️ The Valider footer button is the ONLY validation button. There is NO "Valider la facture" button further down the panel. Do not look for a second Valider after the commit.

The PDF preview panel (left side of the detail panel) intercepts clicks on the underlying table rows. Always close the panel via the cross before clicking another row.

🔑 Panel close cross = button with a mat-icon whose data-mat-icon-name === 't-ic_close-bold-filled' located at top < 50px and width ≥ 30px. There are 3 close candidates in the DOM — that one is the only one that closes the dialog. The tc_icon-close icon at roughly (1022, 52) does NOT close the panel (different role). Reliable Playwright selector:

page.locator('button').filter({ has: page.locator('mat-icon[data-mat-icon-name="t-ic_close-bold-filled"]') }).first()

Step 7 — Batch recap and tracking files

At the end of the batch, update two files at the root of receipts/:

• receipts/_tiime_uploaded.md — exhaustive list (grouped by month) of the pieces whose Tiime metadata has been enriched. Per-line format: - [YYYY-MM-DD] yaml_name — note of the actions. Reference to avoid reprocessing in a future session.
• receipts/_tiime_blockers.md — pieces set aside during the batch, grouped by action type (to delete / comment to replace / nonexistent label / piece not found / arbitration needed). Format: - [YYYY-MM-DD] yaml_name — REASON — REQUESTED_ACTION.

At the start of each session, read receipts/_tiime_uploaded.md and exclude the pieces already listed.

Produce as output:

• Pieces successfully enriched (with no. and label)
• Pieces pending with reason (critical alert, unhandled currency, etc.)
• Anomalies to report to the accountant (recategorizations, vat to adjust, etc.)

Stable Playwright selectors (tested on Tiime 2026-05)

Always prefer getByRole / getByLabel / getByPlaceholder to generated CSS selectors.

Action	Selector
Nav Dépenses → Factures	getByRole('link', { name: 'Factures' }) (submenu unfolded)
Search in invoices	getByPlaceholder('Rechercher dans mes factures...')
Import a document	getByRole('button', { name: 'Importer un document' })
Click an invoice row	getByRole('row', { name: '{date} {merchant}.' }) (short date type "01 avr.")
Voir plus / Voir moins	getByRole('button', { name: 'Voir plus' }) / 'Voir moins'
Nom du document	getByLabel('Nom du document') (textbox above)
Date	textbox under the "Date" label (placeholder "Aucune information")
Date d'échéance	textbox under "Date d'échéance"
Intitulé	textbox under "Intitulé"
Montant TTC	spinbutton in the "Montant TTC" block
Total TVA	spinbutton in the "Total TVA" block
Facture n°	textbox under "Facture n°"
SIREN/SIRET	textbox under "SIREN/SIRET"
N° TVA intracommunautaire	textbox under "N° TVA intracommunautaire"
Invoice comment (on /expense/expense-invoice)	textarea with getByPlaceholder('Ajouter un commentaire')
Bank transaction comment (on /account/transactions)	tr.cdk-row input[placeholder="Ajouter un commentaire"] — cf. §4.3.bis
Label selector	app-label-selector button.label-button (data-cy label__btn-add) — opens an overlay .cdk-overlay-pane.tiime-overlay-panel with 5 suggestions + free search

Changing a Label (label != OCR tag)

Essential distinction: the Label column in the table shows either (a) a structured Tiime Label (mappable to a gl_account), or (b) a category auto-deduced by OCR (LOCATIONS DIVERSES, etc.) when no Label is attached.

Two states of the Label selector:

• 🆕 No label attached: presence of app-label-selector button.label-button[data-cy="label__btn-add"] (with text "Ajouter un label"). Clicking this button opens the picker.
• ✏️ Label already attached: presence of app-label-chip[data-cy="label__btn-edit"] (the chip itself is clickable). Clicking the chip opens the picker in edit mode.

The helper must test both selectors in order (label-chip[data-cy="label__btn-edit"] first, fallback label-button[data-cy="label__btn-add"]).

Procedure to change / set the Label:

1. Click the opener (chip or button depending on state)
2. An overlay .cdk-overlay-pane.tiime-overlay-panel opens with a Suggestions section (5 most relevant labels) + an <input> free-search field
3. To filter the full list: type in the input (e.g. récep, fourni, materiel) — the options match on the label name.
4. Click the <span class="right-padded"> carrying the target label text. The click propagates to the parent row which is cursor: pointer.
5. The overlay closes automatically, the app-label-selector now shows the initials + label name (e.g. PM PETITS MATERIELS ET FOURNITURES)
6. "Annuler / Valider" footer appears → validate as for the other edits

Creating a new Label in Tiime

When the target label does not exist in the database (e.g. RECEPTIONS FRAIS DE REPRESENTATION for client meals), Tiime exposes a "Créer le label" action directly in the selector overlay — no need to go to Paramètres.

Procedure:

1. Open the selector (cf. above)
2. Type in the input the exact desired label name (e.g. RECEPTIONS FRAIS DE REPRESENTATION)
3. If no label matches, the overlay shows a single item "Créer le label" (exact text). Click it.
4. The label is created in the database + immediately applied to the current piece.
5. "Annuler / Valider" footer appears → validate.

Once created, the label becomes available in all future searches for this company. Ideal for relabeling series: 1st piece → creates the label; following ones → standard search.

Tiime label → gl_account mapping (to be enriched as cases arise):

• HONORAIRES → 622600
• HOTEL → 625100
• RESTAURANT → 625610
• PETITS MATERIELS ET FOURNITURES → 606800
• LOCATIONS DIVERSES → 613500 (to avoid for IT hardware — recat 606800)
• AMAZON → 606800 (Tiime label used for Amazon hardware specifically)
• PARKING → 625300 or 625400
• ASSURANCE → 616xxx

⚠️ The numeric refs (e2210, etc.) are not stable between snapshots — always regenerate a snapshot before each action and use accessible selectors.

Datepicker — opening and navigation

The trigger is app-document-date-metadata > .datepicker-trigger (a <span>, not a button). Direct JS click works.

Once open, the calendar exposes:

• button[aria-label="X mois YYYY"] for each day (clickable directly via their aria-label)
• .mat-icon.tiime-mat-calendar-previous-button and ...next-button for navigation (these are icons, not <button> — click directly on them). The calendar always opens on the current month, so N previous clicks depending on the gap.

⚠️ Once the calendar is open, the backdrop intercepts native Playwright clicks (TimeoutError "intercepts pointer events"). Prefer browser_evaluate with a direct JS click() for calendar navigation.

Datepicker — multi-year view (for corrupted dates like "0006")

The Tiime datepicker exposes a multi-year mode to quickly jump from one year to another, indispensable when the original date is very far (corrupted OCR date, etc.).

Three view levels in the calendar:

• mat-month-view (days of a month)
• mat-year-view (months of a year)
• mat-multi-year-view (24-year view per page)

Period button: <div class="mat-calendar-period-button" role="button"> (NOT an HTML <button> — selector document.querySelector('.mat-calendar-period-button')). Clicking it goes up one level: month → year → multi-year.

Navigation between 24-year slices: .tiime-mat-calendar-next-button (icon, not button) — each click advances 24 years in the multi-year view. To go from 0006 to 2026: ~84 next clicks. JS loop:

for (let i = 0; i < 84; i++) { next.click(); await new Promise(r => setTimeout(r, 30)); }

Then click the year via button[aria-label="2026"] → returns to year-view (months). Click the month (button[aria-label="janvier 2026"] or partial aria-label) → returns to month-view (days). Click the day via button[aria-label="6 janvier 2026"].

Deleting a piece in Tiime

To delete a piece (duplicate, empty row, etc.):

1. Click the row to open the detail panel
2. Click the actions button: button[data-cy="document-informations__btn-actions"] (icon t-ic_more-material-filled at the top of the panel, ~top=102, left=1142)
3. A menu opens with a single option: "Supprimer" (selector .mat-mdc-menu-item with exact text)
4. Click "Supprimer" → confirmation dialog opens (mat-dialog-container) with text "Êtes-vous sûr de vouloir supprimer 'X' ?"
5. Click the "Supprimer" button in the dialog (NOT the "Annuler" button) → effective deletion.

Manual PDF upload (case of a piece absent from Tiime)

For pieces with no Tiime entry created by the Revolut sync (personal payments, invoices outside the bank flow):

1. Navigate to /expense/expense-invoice
2. Click the "Importer un document" button (selector button with exact text, at the top of the table)
3. A modal file chooser opens — Playwright MCP captures it via the state Modal state: [File chooser]
4. Call browser_file_upload({ paths: ["/absolute/path/file.pdf"] }) to provide the file
5. Tiime runs the OCR (can take several minutes) → the new entry eventually appears in the Factures flow

⚠️ Post-upload not guaranteed: observation 2026-05, the uploaded PDF may be routed to a separate OCR inbox (cf. the "Demandes" counter on the home, which goes from 1 to 2). The new entry is not immediately visible in /expense/expense-invoice even after several minutes. Recommended action: after upload, set the piece as a blocker for manual verification by the user in /companies/{id}/home ("Demande accountant" card).

Overwrite vs preserve the existing comment

Two helpers needed depending on the case:

• processPiece (set-if-empty) — only writes the comment if empty. Avoids overwriting a comment entered manually by the user (e.g. "repas midi avant départ Islande" on Mozza).
• overwriteComment (force) — always writes, overwrites the existing one. Needed for:
  • Tiime auto-generated "batch cooking" comments like "repas midi entrées plats dessert semaine X" (to replace with an audit-compliant version)
  • Pieces whose initial OCR comment does not comply with the project conventions

Reusable helper pattern:

async function processPiece(rowMatch, tvaIntracom, commentaire, opts = {}) {
  // 1. click row, voir plus, fill (tva intracom, commentaire IF empty or opts.overwrite)
  // 2. validate footer, close panel
}

Imposed URL filters and sort

Tiime rewrites the URL of the invoice list with default parameters:

• ?sort=metadata.date:desc (date desc sort forced — metadata.created_at:desc not supported)
• &accountable=true&with_total_amount=true&with_total_amount_excluding_taxes=true

Consequence: pieces without total_amount (amount 0 €, OCR pending, etc.) are filtered out of the default view. To see them, navigate with ?sort=metadata.date:desc ALONE (Tiime may still add the filters). The filter is not disableable via URL — you have to go through the UI or accept they are invisible on the script side.

Special cases

Foreign currency (e.g. SSP Iceland in ISK)

• Tiime exposes the Montant en devise field under "Voir plus".
• Get the ECB rate of the piece's day via WebFetch (https://www.ecb.europa.eu/...) or an equivalent source.
• Enter the foreign-currency amount in the dedicated field and the EUR amount in Montant TTC.
• Non-EU foreign vat: not recoverable → leave 0 in Total TVA and book the whole charge as total_excl_tax (account 625100 for meals while traveling).

Piece without SIRET (only RCS / intra-EU VAT)

• For FR suppliers: SIREN = first 9 digits of the intra-EU VAT number (after the country code + check key). E.g. VAT FR19911075380 → SIREN 911075380.
• For EU/NON-EU suppliers: leave SIREN/SIRET empty, fill only the intra-EU VAT number.

Conditional piece (corporate_tax status conditional)

• Upload possible if the taxpayer decision is settled (prior_decision not null) — the decision will be arbitrated later with the accountant.
• Otherwise, ask the user for the arbitration before upload.

Piece with alert RECEIPT_PARTIAL

• DO NOT upload. Planet Sushi 16/04 case: "Document non accountant" receipt — wait for the real invoice.

Piece whose name starts with "Document — ..."

Indicates that Tiime auto-created the entry from the bank sync without a PDF being attached. The receipt may still already be attached: the preview is an <img> with src="blob:...", not a PDF canvas — adapt the detection selector accordingly. If really no receipt is attached, use the hidden input[type=file] of the action bar (data-cy="..."; Playwright setInputFiles bypasses the display:none).

In all cases, rename "Document" with a business name (<input formcontrolname="name">) to clarify the list.

Best practices kept from the 2026-04 batch

1. For chained edits: a JS eval that groups (set values → Valider → close → click next row) — much more efficient than 4 separate actions via browser_click.
2. Always use the native value setter on <input> / <textarea> (Object.getOwnPropertyDescriptor(HTMLInputElement.prototype, 'value').set) then dispatch input + change + blur to reactivate the Angular FormControl. Otherwise Tiime does not detect the change and the Valider footer does not appear.
3. The datepicker always opens on the current month → loop of previous clicks. For 2026-04 from May: 1 click. Anti-pattern: trying fill() on the date input — it is readonly.
4. The lethal-trifecta hook blocks WebFetch after Playwright access to Tiime (financial data). Any currency conversion / external lookup must be done by the user or pre-done before the session.
5. The hook can also block browser_evaluate if the code contains a numeric value that looks like fetched external data (false positive). Reformulating the comment without the numeric value unblocks it.
6. Tiime label ↔ desired gl_account mismatch: when no Tiime label maps to the target account, pick the least wrong one and specify the desired gl_account in the comment for the accountant (e.g. "compte 606300" for an office coffee labeled PETITS MATERIELS ET FOURNITURES).
7. Fix the YAML when Tiime has better data: Tiime OCR is often more reliable than the YAML extraction for SIRET / intra-EU VAT. Cross-check via the Luhn key of the VAT number (the 9 digits after "FR{key}" must match the SIREN of the SIRET).
8. Label creation in series: create the newly required label on the 1st piece (via the picker's "Créer le label"), then apply it to the following pieces by standard search. The label becomes available for all pieces as soon as it is created.
9. For conditional pieces (TAXPAYER_POSITION, Picard/Otera Sunday, Plaisirs et Gourmandises lunch): standardized comment "Repas indiv. / courses — position contribuable AN nourriture (cabinet)." — lets you find all the relevant pieces by text search.
10. For client meals: if the RECEPTIONS FRAIS DE REPRESENTATION label exists → apply it. Otherwise create the label then apply it (cf. §"Creating a new Label").
11. For multi-month but not-found pieces: use ASC sort (?sort=metadata.date:asc) to start from the oldest. Tiime forces desc in the URL rewrite, but the initial ASC stays applied in the session until the next reload.

Observed anti-patterns

• ❌ Clicking a tr.cdk-row when the preview panel is open: the PDF intercepts the click. Close the panel first via the t-ic_close-bold-filled cross.
• ❌ Using the snapshot eXXXX refs between two interactions: they are not stable. Prefer getByRole / semantic CSS selectors (tr.cdk-row, app-document-string-metadata, etc.) or a JS eval.
• ❌ Clicking tc_icon-close thinking it is the panel close cross — it is a different button. The right cross is data-mat-icon-name="t-ic_close-bold-filled" at top < 50px and width ≥ 30px.
• ❌ Clicking the footer "Valider" thinking it is insufficient: it is THE commit button. There is no separate "Valider la facture" button further down. The cross only serves to close the panel afterwards.
• ❌ Looking for a <button> for the datepicker period button — it is a <div role="button">. Correct selector: document.querySelector('.mat-calendar-period-button').
• ❌ Trying WebFetch to verify an exchange rate after Tiime access — blocked by the lethal-trifecta hook. Do the lookup before the session, or ask the user for the rate.
• ❌ Sending the user back to the Tiime home when an uploaded piece was not found — say clearly "I didn't find it, here is where you can look: Demandes card / Documents submenu". Don't pretend to open it if you don't know where it is.
• ❌ Filling only the Invoice comment without filling the bank transaction comment (/account/transactions) — the user looking at the transactions list then sees no annotation. Cf. §4.3.bis. Always fill both, especially for recurring charges (FRAIS BANCAIRES, ASSURANCE, SaaS subscriptions).

Reusable pattern: processPiece helper

To process a batch of pieces, define a utility function that chains click row → Voir plus → set fields → Valider → close in a single browser_evaluate:

async function processPiece(rowMatch, tvaIntracom, commentaire) {
  // 1. Click row by text match
  for (const r of document.querySelectorAll('tr.cdk-row')) {
    if (rowMatch.every(m => r.textContent.includes(m))) { r.click(); break; }
  }
  await new Promise(r => setTimeout(r, 700));
  // 2. Voir plus
  for (const b of document.querySelectorAll('button')) {
    if ((b.textContent || '').trim().startsWith('Voir plus')) { b.click(); break; }
  }
  await new Promise(r => setTimeout(r, 400));
  // 3. Set TVA intracom + commentaire (only if empty)
  const inpSetter = Object.getOwnPropertyDescriptor(HTMLInputElement.prototype, 'value').set;
  const taSetter = Object.getOwnPropertyDescriptor(HTMLTextAreaElement.prototype, 'value').set;
  document.querySelectorAll('app-document-string-metadata').forEach(el => {
    const input = el.querySelector('input');
    if (input && el.textContent.includes('TVA intracommunautaire') && !input.value && tvaIntracom) {
      inpSetter.call(input, tvaIntracom);
      ['input','change','blur'].forEach(e => input.dispatchEvent(new Event(e, { bubbles: true })));
    }
  });
  const ta = document.querySelector('textarea[placeholder*="ommentaire"]');
  if (ta && !ta.value && commentaire) {
    taSetter.call(ta, commentaire);
    ['input','change','blur'].forEach(e => ta.dispatchEvent(new Event(e, { bubbles: true })));
  }
  await new Promise(r => setTimeout(r, 500));
  // 4. Valider + close
  for (const b of document.querySelectorAll('button')) {
    if (b.textContent.trim() === 'Valider') { b.click(); break; }
  }
  await new Promise(r => setTimeout(r, 700));
  for (const b of document.querySelectorAll('button')) {
    const ic = b.querySelector('mat-icon');
    const iconName = ic ? ic.getAttribute('data-mat-icon-name') : null;
    const rr = b.getBoundingClientRect();
    if (iconName === 't-ic_close-bold-filled' && rr.top < 50 && rr.width > 30) { b.click(); break; }
  }
  await new Promise(r => setTimeout(r, 500));
}

Observed performance: ~2-3 seconds per piece. For a batch of 50+ pieces, use this pattern in browser_evaluate with an array of pieces to process in series.

⚠️ Important: this processPiece helper enriches the Invoice on /expense/expense-invoice. It does NOT fill the bank transaction comment on /account/transactions (cf. §4.3.bis). For recurring charges mostly visible from the transactions list, add a second pass via the helper below.

Reusable pattern: setBankTransactionComment helper

To fill the per-row comment of each bank transaction on /account/transactions (cf. §4.3.bis):

// On /account/transactions
async function setBankTransactionComments(targets) {
  // targets = [{ match: ['12 janv.', '-35,00', 'Company Pro plan fee'], comment: '...' }, ...]
  const inpSetter = Object.getOwnPropertyDescriptor(HTMLInputElement.prototype, 'value').set;
  const results = [];
  for (const t of targets) {
    const rows = Array.from(document.querySelectorAll('tr.cdk-row'));
    const row = rows.find(r => t.match.every(m => r.textContent.includes(m)));
    if (!row) { results.push({ match: t.match.join(' / '), status: 'not found' }); continue; }
    const input = row.querySelector('input[placeholder="Ajouter un commentaire"]');
    if (!input) { results.push({ status: 'no input' }); continue; }
    if (input.value) { results.push({ status: 'already filled', existing: input.value }); continue; }
    inpSetter.call(input, t.comment);
    ['input', 'change', 'blur'].forEach(e => input.dispatchEvent(new Event(e, { bubbles: true })));
    await new Promise(r => setTimeout(r, 350));
    results.push({ match: t.match.join(' / '), status: 'set' });
  }
  return results;
}

Performance: ~400 ms per transaction. No need to open a detail panel — the input is inline on the row. Persistence verifiable after a page reload.

When to use this helper:

• Recurring charges (FRAIS BANCAIRES Revolut Business, ASSURANCE Alan, SaaS subscriptions Tiime/Notion/etc.)
• Cases where Gérard mostly looks at the bank transactions list (quick overview workflow)
• Complement the processPiece (Invoice) already applied — the 2 comments are independent

Skill maintenance

To update when:

• Tiime changes its DOM (broken selectors)
• New mapping case encountered (category, currency, exotic supplier)
• New accountant arbitration rule
• New Tiime OCR quirk

See also

• justificatif-describe (upstream skill — produces the YAML)
• enrich-justificatifs (upstream skill — completes the YAML with Gérard's info)
• bootstrap-projet (context loading)
• Memory audit_decisions_2026-05.md — for the decided recategorizations