Pending imports

The Pending imports screen is an inbox: this is where bank movements that arrive on their own into Cuéntamo (through an integration, an automation or the public API) pile up when Cuéntamo could not place them with confidence. Instead of creating them blindly or silently discarding them, it sets them aside so you can review them and decide what to do with each one.

The difference with Import file is the origin. There, you upload the statement by hand and control the whole process from start to finish. Here the movements come in by themselves, without you being present: something (an external service, a script of yours, an automation that sends each operation the moment your bank records it) pushes them into Cuéntamo through the API. This screen is where they rest until you give them the green light.

Nothing is saved as a real movement without your confirmation. Whatever arrives this way stays "pending"; it only becomes a real movement when you import it from here.

What it is for: reviewing what comes in automatically

Cuéntamo can receive bank movements in real time through its public API, authenticated with a personal access token (the tokens you manage in Settings). The idea is that, if you have an integration or a small automation connected to your bank, each operation reaches Cuéntamo as soon as it happens, without waiting until month-end to download the statement.

When a movement arrives this way, Cuéntamo tries to place it on its own. If it is completely sure (for example, it matches exactly a forecast you already had), it applies it without bothering you. But if there is any doubt — it cannot find anything to pair it with, there are several candidate forecasts, or the amount does not quite add up — it does not take the risk: it sets it aside in this pending inbox so that the last word is yours.

That way you get the best of both worlds: the convenience of movements coming in on their own and the peace of mind that nothing doubtful sneaks into your accounts without your approval.

The sidebar alert

The Pending imports entry in the side menu only appears when there is something to review. If the inbox is empty, it does not even show up: it does not clutter your menu with sections you do not need.

When there are movements waiting, the entry shows up with an amber badge and a figure over the icon with the exact number of pending items (if it goes above 99, it shows "99+"). It is the "you have things to approve" alert: as soon as you resolve everything, the entry and its counter disappear from the menu.

The list, grouped by incoming account

When you open the screen you see a header with the total number of pending items and, below it, the movements grouped by their incoming account: the source bank account as identified by the integration (an IBAN or an account number). Within each group, movements are ordered by ascending date (oldest first), the way you review a statement.

Each group header shows the incoming account, how many movements it holds and, if it is already mapped, which Cuéntamo account it points to. Movements that arrived without identifying their source account are grouped separately, as "Unidentified".

When the group is already mapped, each movement includes a "View movements" link that opens a side panel, without leaving the inbox, with the account's list: its real and forecast movements with the running balance (a line marks "Today", separating the real from the forecast). The panel jumps to and highlights the date of the movement you're reviewing, so you see its balance context at a glance, and it includes a search box (by concept, category or amount) and a "Go to today" button. It's how you check the context and decide sensibly what to import, what's a duplicate and what isn't.

Associating an incoming account with one of yours

When the integration could not tell which Cuéntamo account a group of movements belongs to, the group header offers an "Associate to account…" selector. You pick one of your accounts and press Associate: that account is assigned in one go to every movement in the group, with no need to go one by one.

If you tick "Remember for future imports", Cuéntamo stores that mapping on the account (its external reference), so that next time movements arrive from that same bank account they are matched automatically, without asking you again. If the group was already mapped, the same selector lets you change it to a different account.

Assigning the account to a single movement (and finding its forecast)

Besides the group selector, every movement without an account has its own selector: "No account assigned. Pick one to look for a forecast". It is the way to do it one by one when different movements from the same incoming account go to different accounts of yours.

The interesting part is what happens when you assign it (both per row and with the group's "Associate to account" button): Cuéntamo runs each movement through the matching engine again, now against the movements of the account you just chose. It matches its forecasts ("confirm the forecast" appears), detects the ones you already have recorded, and leaves as new only the ones that truly are. That way you don't lose the automatic match just because the account arrived unidentified.

Movements you already have (possible duplicates)

When you assign the account, Cuéntamo cross-checks each incoming movement against the ones you already have recorded in it. Those matching an existing movement are grouped separately, under the "You already have these" collapsible, collapsed by default so they don't clutter the list. They are assumed correct: their default action is "I already have it" (don't import), so if you touch nothing, they aren't duplicated.

You can expand them to review one by one: each card shows the existing movement it matches (by amount and date; "you already have it" if exact, "you may already have it" if the date is a couple of days off). If one turns out to be genuinely new, switch it to "Import anyway".

When you confirm below, the ones you leave as "I already have it" also do a small merge: the bank reference is linked to the movement you already had (which often didn't carry one, having been entered by hand). With that, subsequent syncs recognise that movement and don't queue it again.

What each movement shows

Each pending item is presented as a card with the information that came from the bank:

• The concept exactly as the bank sent it.
• The operation date, the Cuéntamo account it is destined for and, if it came, the bank reference (the unique identifier of the operation, marked as "ref:").
• The amount, in green if it is an income (with a "+" in front) or in red if it is an expense.

In the doubtful or suggested groups, the card adds a confidence bar (green high, amber medium, red low) with the certainty percentage, and next to it the details of the candidate forecast: its concept, its amount and its date. That way you see at a glance what movement it proposes to pair with and decide whether it makes sense.

If the integration sends extra information about the movement (counterparty, operation type, bank category, SEPA reference, or any loose field from the source), the card shows a "Details" expander. Cuéntamo keeps that data exactly as it arrives, even without interpreting it, so nothing is lost. Note: what shows up depends on what the bank provides; data like the supply address of a utility bill usually doesn't travel in the bank entry (it lives on the invoice), so it may not be there.

Resolving an unmatched movement

For unmatched pending items, each card offers three decisions as buttons:

• Create movement (green): turn it into a real movement in the stated account. This is what you will do with the legitimate pending items you want to keep.
• Do not import (red): discard it. Use it when it is something you do not want in your accounts (a duplicate, a test operation, something you have no interest in recording). It disappears from the inbox without creating anything. It is a one-off decision: it is not remembered. If that same movement is imported again later, it will reappear in the inbox for you to decide anew.
• Later (grey): leave it as it is to decide another time. It is the default option: as long as you touch nothing, the movement stays pending.

When you choose Create movement, two fields appear to fine-tune the entry: one to edit the concept (in case the bank one is cryptic) and a category selector. Cuéntamo suggests a category automatically from the concept and pre-selects it; you can accept it or change it. The selector only offers you categories of the right type (expense if it is a charge, income if it is a credit).

If you have the freelance module enabled, a "Freelance" checkbox also appears: tick it so the movement has freelance scope and gets its entry in the record book. When ticked, you can pick the VAT rate (the ones your tax regime offers), which is seeded on the document. That way you classify a deductible expense right when you import it, with no need to edit it later. The checkbox appears both when creating a new entry and when confirming a forecast; on confirm it adopts the scope and VAT the forecast already had (and you can change them — including switching it back to personal, which archives its document).

Above the concept a suggestion may appear (a button with ✎): it's how you yourself named movements with that same bank concept before. One click fills it in, so you don't rewrite the bank's "Recibo …" every time.

Resolving a movement with a likely pair

For pending items with a doubtful or suggested match, the decisions change, because on top of importing you can confirm the forecast that Cuéntamo believes corresponds:

• Confirm forecast (green): you accept the pair. The candidate forecast becomes the real movement for this operation, instead of creating a duplicate. It inherits the forecast's concept and category: it asks you for nothing, because the movement already knows what it is. If you want to fine-tune it later, edit it from Movements. And if the forecast you confirm is one leg of a transfer, the other leg is confirmed automatically (a transfer is a single two-legged movement): it never stays half-done.
• Create new (blue): ignore the proposed pair and create a new, independent movement. Use it when the candidate is not really the same payment. Here the concept and category fields do appear (with the automatic suggestion).
• Do not import (red): discard it, just as in the unmatched case.
• Later (grey): leave it pending for later.

Confirming forecasts from here is one of the legitimate ways a forecast becomes a real movement: it is your explicit confirmation, not an automation behind your back.

Pairing by hand (even if it doesn't match at first)

When a movement doesn't match on its own, or the automatic match picks the wrong one (two similar bills, two instalments in the same month…), you have the "Find a match" link. It appears on any movement with an account, matched or not.

When you press it, Cuéntamo lists candidates from that account, close in date and of the same sign, in two groups:

• Forecasts (confirm): you pick the right forecast and, on apply, it is confirmed as the real movement (instead of creating a duplicate).
• Existing (pair): real movements you already have (still without a bank reference). If you pick one, you tell Cuéntamo "I already have this, it's this one": nothing is imported and a merge happens (the bank reference is linked to the existing movement, so it won't queue again). It's the manual route for cases the automatic detection misses (dates far apart, amounts that don't match to the cent).

A forecast already claimed by another movement in the same batch does not appear: that way you don't confirm the same forecast twice.

One forecast for several movements

It can happen that you assign several incoming movements to the same forecast (for example, a purchase the bank charged you in two parts). Cuéntamo prevents this by default, but if you really want it, when you apply it asks you case by case how to import it, with two options:

• The closest confirms the forecast: the movement closest by date confirms the forecast (with its amount) and the others are created as new, independent movements. It keeps one line per bank entry.
• Sum into the forecast: the forecast is confirmed as a single entry whose amount is the sum of the assigned movements. Handy when you want to see that expense as one entry.

You choose for each conflicting forecast, and then it all imports together.

Combining several movements into one

Sometimes the bank splits a single movement of yours into several charges: the classic case is a foreign-currency purchase plus its exchange fee, which arrive as two separate entries even though you keep them (or want to keep them) as one movement on the card. That's what Combine is for.

Each inbox row has a selection checkbox on the left. Tick the ones you want to merge —they must be from the same account— and the "Combine" button appears in the bottom bar. When you press it, you choose the destination:

• Into an existing movement: link the selected entries to a movement you already have in the account (for example, that single charge you entered by hand). Cuéntamo lists the nearby movements for you to pick. If the sum of the entries doesn't match the movement's amount, it warns you of the difference and lets you, if you wish, adjust the amount to the total (by default it leaves it untouched).
• Into a new movement: it creates a single movement whose amount is the sum of the entries, with the concept and category you set.

Whichever destination you combine into, Cuéntamo stores the bank references of all the entries on that movement. So if those same charges are imported again in the future, they are recognised as already recorded and don't slip back in. That's how "several bank entries = one movement in Cuéntamo" stays properly tied down for future imports too.

Deduplication by bank reference

When movements arrive on their own and in real time, the biggest risk is entering the same thing twice: that the integration resends an operation you had already recorded, or that it overlaps with what you already imported by hand from a statement. Cuéntamo avoids this with the bank reference, that unique identifier that accompanies each operation.

If a movement coming in through the API carries a reference that already exists in your data, Cuéntamo recognises it as a duplicate and applies or discards it automatically, without filling your inbox with repeats. That is why what ends up reaching this screen is, above all, the genuinely new or doubtful: the repeated is filtered out before it bothers you.

The reference you see on each card (the "ref:") is precisely that identifier. If you want deduplication to work smoothly, it helps for your accounts and your integration to handle these references properly.

What if you import something you had already verified by hand? It is not duplicated. Cuéntamo recognises it as already existing —by its reference, or by matching in date and amount with a real movement of yours— and skips it. This is also checked when you assign the account to a movement that arrived without one: if, upon assigning it, it turns out it already existed as a verified movement, the card is discarded as a duplicate and you are told, instead of being offered to create a copy.

Undoing an import returns the rows to the inbox. If you apply an import and then undo it (with Ctrl/Cmd+Z, or with "Undo from the discrepancy" when a reconciliation breaks), Cuéntamo doesn't just delete the created movements: it also reopens the corresponding rows in this inbox, so you can review them and decide again. Redo (Ctrl/Cmd+Shift+Z) resolves them once more.

Dismissing everything, or just one incoming account

In the top right there is a "Dismiss all" button. It marks all pending items as "do not import" in one go. It is handy when a batch you do not care about arrives (for example, after testing your integration) and you prefer to empty the inbox without going one by one.

And if you only want to get rid of the movements from one specific incoming account (a bank account you don't want to process), its group header has a "Don't import" button: it marks every movement in that group at once. Press it again to undo.

Note: both mark the decision, but it is not applied until you confirm below, so you can still change your mind before pressing the final button.

When the source has handed over the account's entire history and you only want to keep the recent part (this happens with some banks the first time you connect them), the group has a "Delete earlier than…" action: you pick a date, Cuéntamo tells you how many rows will be deleted, and on confirming it removes from the inbox only what predates that day for that incoming account. And if what's left over is the odd movement, each row has its own bin.

Neither of these creates rules: they delete what's there now and change nothing about what arrives tomorrow. That's the important difference from dismissing, and it's why every action on the screen tells you whether it affects just that movement or is remembered for the next ones.

If what you want is to remove them entirely, leaving no trace —data that arrived by mistake from an account you won't process—, each group also has an "Ignore and delete" button. Unlike "Don't import", this one is immediate (it doesn't wait for you to confirm below) and deletes those movements from the inbox for good: they aren't kept as "dismissed" and can't be recovered. To stop receiving them going forward, stop sending that account from Habeas.

The bottom bar and applying the changes

Nothing you decide runs instantly: first you spread decisions across the cards and then you apply them all together. At the bottom there is a fixed bar that summarises what you are about to do:

• How many movements you are going to import (in green): the ones you marked as "create movement" or "confirm forecast".
• How many you are going to dismiss (in grey): the ones marked as "do not import".
• If you have not decided anything yet, the bar invites you to choose an action.

The pending items you leave as "Later" do not count: they stay just as they are in the inbox for next time. When you are happy, press the "Apply" button. Only then does Cuéntamo create the movements, confirm the paired forecasts and remove from the inbox what you have discarded. The button stays disabled while there is nothing to apply.

The final summary

On applying, Cuéntamo shows you a summary of what happened: how many movements were imported, how many were dismissed and, where applicable, how many matching rules were created along the way (so that similar operations place themselves on their own in the future). From there, a button takes you straight to the movements list to check how they turned out. And if there are still pending items to review (you left some as "later"), a "Continue with pending" button also appears, to go back to the inbox without leaving the screen.

The movements you resolved update the balance of their account like any other entry. And since the sidebar counter is recalculated, you will see the amber badge go down or disappear depending on what you left pending.

When the inbox is empty

If there is nothing to review, the screen tells you so with a calm message and no movements in the list. It is not an error: it means nothing has come in through an integration since last time, or that you already resolved everything. Since the side menu entry only appears when there are pending items, you will normally only visit this screen when the amber badge warns you there is work to do.

Its sibling: the Pending investments inbox

There is a second, twin inbox for what comes from a broker (for example, through an integration like Habeas): Pending investments. It works just like this one, but instead of bank movements it collects investment operations —buys, sells, dividends— and broker cash movements that Cuéntamo could not assign to an account.

Previously, a broker movement with no recognised account was discarded; now it is never lost: it lands in this inbox for you to review. It appears in the side menu, with its own amber badge and counter, only when there is something pending.

The mechanics are the ones you already know: movements are grouped by their originating broker account; in each group's header you associate that origin with one of your accounts (with the option to remember the mapping for next time), and each card lets you Import, Don't import or leave it for Later. On apply, whatever you import becomes investment operations in the chosen account (deduplicated by their reference, so nothing already recorded is repeated). The rest of the flow —the bottom bar, the final summary— is identical.

Requirements and availability

This inbox is fed by Cuéntamo's public API, which is authenticated with personal access tokens. Creating and managing those tokens, as well as connecting an integration that pushes movements, is a feature of the higher plans; you will find token management in Settings.

If you do not use any integration of this kind, it is normal that you never see this screen in the menu: you do not need it. Your way to enter movements in bulk remains Import file, uploading the statement yourself whenever you want.