> ## Documentation Index > Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt > Use this file to discover all available pages before exploring further. # Resolve Actuals Exceptions > Review unmatched invoice spend, create audited manual allocations, and correct automatic budget matches The **Unmatched exceptions** queue contains invoice events that MSPortal could not allocate fully and automatic matches that a user moved aside for review. Resolve the queue to make each locked budget line's actual spend complete and explainable. ## Prerequisites * An Approved or Archived budget with access to the **Actuals** tab * Permission to edit budgets for allocating, removing, moving, or restoring reconciliation decisions * Synchronized invoice data in the same currency as the locked budget Users without budget write permission can review exceptions, matched evidence, and active allocation details but cannot change them. ## Getting Started Open the locked budget in View mode, select **Actuals**, and scroll to **Unmatched exceptions**. Check the provider, invoice details, source amount, remaining amount, currency, and exception reason before selecting a line. Choose the eligible budget line that should receive the spend. Rejected lines are not available because they are outside the approved baseline. Enter a non-zero amount with up to four decimal places, using the same sign as the remaining amount. Its magnitude cannot exceed the remainder. The remaining amount is filled in by default; keep credit allocations negative. Click **Allocate**, then confirm that the summary, line outcome, and remaining exception amount update. ## Understand Exception Reasons | Reason | What it means | What to do | | ----------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | **No matching reference** | No exact reference, captured project, or product identity identified one line | Select the correct line and allocate the amount | | **Multiple possible lines** | The best automatic method identified more than one line | Review the invoice detail, then allocate it manually | | **Currency mismatch** | The source currency differs from the locked budget currency | Correct an inaccurate source currency and resync; genuine foreign-currency spend cannot be allocated to this budget | | **Currency unknown** | Neither the invoice nor company or tenant configuration supplied a usable currency | Set the correct currency at the source or company/tenant level, then resync | | **Moved to exceptions** | A user paused an automatic match | Allocate it manually, or correct the source information and restore automatic matching | | **Source changed since allocation** | Synchronized source details changed after a manual allocation or exclusion | Review the new source, then remove or restore the previous decision | | **Partially allocated** | Only part of the source amount has been assigned | Allocate the remaining amount, possibly to another line | Currency mismatch and unknown-currency events cannot be manually allocated. MSPortal does not perform foreign-exchange conversion against a locked baseline. ## Split Spend Across Budget Lines You can allocate one invoice event across more than one eligible budget line. Select the first line, replace the default amount with that line's share, and click **Allocate**. The event stays in **Unmatched exceptions** as **Partially allocated** and shows the amount still unallocated. Select another eligible line and allocate all or part of the remaining signed amount. Repeat until the event is fully allocated. Manual allocation suppresses automatic matching for the entire source event. This prevents the same invoice spend from being counted both automatically and manually. ## Correct an Automatic Match If an invoice event matched the wrong line, move it to exceptions so you can allocate it yourself or correct the source and retry automatic matching. In **Line outcomes**, click the **Review** button showing the event count on the incorrectly matched line. Click **Move to exceptions**. The event is removed from the line and automatic matching is paused. Its amount still contributes to overall Actual spend and becomes unallocated; this does not exclude the invoice from spending totals. To override the match, select the correct line in **Unmatched exceptions**, enter the amount, and click **Allocate**. You can split it across lines without restoring the original match first. To retry automatic matching instead, correct the reference, project, PO, product, or other source detail in the PSA, allow it to synchronize, then click **Restore match**. MSPortal reconsiders the current source data. Confirm the amount moved to the intended line and review any remaining exception. If automatic matching is still ambiguous, allocate the event manually. ## Manage Manual Allocations The **Manual allocations** table records the source, destination line, allocated amount, operator, time, and source status for every active manual decision. ### Remove a Manual Allocation In **Manual allocations**, locate the invoice event and budget line. Pay particular attention to **Source changed**, which means the synchronized amount or details changed after allocation. Remove the allocation. If it was the event's last manual allocation, MSPortal may resume automatic matching using current source data. Check **Line outcomes** and **Unmatched exceptions**. Reallocate the current amount if necessary. Removing an allocation does not edit the approved budget or the source invoice. It removes the active reconciliation decision while preserving its audit record. The **Manual allocations** table shows active decisions, not a complete list of removed decisions. ## Common Tasks ### Resolve an Ambiguous Product Match Compare the invoice description and SKU with the candidate budget lines. Allocate the event to the intended line, then clean up duplicate or inconsistent product identities before the next budget is approved. ### Handle a Changed Invoice If a PSA update changes an invoice amount or detail, MSPortal flags the old manual decision instead of silently applying it to the new source. Remove the stale allocation, review the updated remaining amount, and allocate it again if automatic matching does not resolve it. ### Restore an Excluded Event Use **Restore match** when the automatic match should be allowed again. Correct the PSA reference or relationship first if restoring the event would otherwise repeat the same incorrect match. ## Troubleshooting | Issue | Resolution | | -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | Allocation controls are disabled | Confirm your role can edit budgets, the event currency matches the budget, and an eligible line exists | | No budget lines are available | Rejected lines cannot receive spend; confirm the approved budget contains at least one eligible line | | Allocation validation fails | Select a line and enter a non-zero amount with no more than four decimal places; its sign must match the remainder and its magnitude cannot exceed it | | The event remains after allocation | Review **Remaining**; a partial allocation stays in the queue until the full signed amount is allocated | | A moved event needs a different line or split | Allocate it directly from the exception queue; restoring the old match first is unnecessary | | A manual allocation says **Source changed** | Remove the stale allocation and review the latest synchronized invoice data | | Removing an allocation rematches the event automatically | This is expected when current project, product, or reference data supplies one unique automatic match | | The wrong line matches again after restore | Correct the reference or relationship in the PSA, let it synchronize, and then restore the event again | ## Best Practices * Resolve the oldest and largest exceptions first * Investigate source and mapping problems before creating recurring manual work * Allocate the exact signed remaining amount, including negative credit amounts * Use a single exact budget reference whenever the PSA workflow supports it * Review **Source changed** warnings promptly * Keep manual allocations limited to genuine exceptions so the audit trail stays meaningful * Review both Unallocated and the exception queue before presenting results; currency exceptions can remain even when Unallocated is zero ## Related Resources * [Track budget actuals](/user-guides/budgets/tracking-budget-actuals) * [Approve and lock a budget](/user-guides/budgets/approving-and-locking-budgets) * [Budgets overview](/user-guides/budgets/index) * [Invoices](/user-guides/invoices/index)