The 5 Source Levels
Every value in a PaisaTax session has a source that records where it came from. When multiple sources provide a value for the same field, the higher-priority source wins.
| Priority | Source | Meaning | Set By |
|---|---|---|---|
| 1 (highest) | override | Preparer intentionally replaced a computed value | Preparer clicks "Override" on a computed field |
| 2 | preparer | Preparer entered or corrected the value manually | Preparer types in wizard or chat |
| 3 | ocr | AI extracted from an uploaded document | Document processing pipeline |
| 4 | upload | Value came from a document upload but not OCR (metadata) | Upload classification |
| 5 (lowest) | system | Computed by the tax engine from other values | Dependency graph calculation |
Info
The rule is simple: human input always beats AI, and AI always beats the system. A preparer correction will never be overwritten by a later OCR extraction or engine recomputation.
What Each Level Means in Practice
Override (Priority 1)
Use override when the tax engine computes a value but you know a different number is correct. Common scenarios:
- Schedule C Line 1 auto-computes from 1099-NEC + 1099-K totals, but the client's actual gross receipts differ
- A depreciation calculation needs a manual adjustment
- The standard deduction applies but you need to force itemized (or vice versa)
Overridden fields show a purple overlay in the PDF prep view so you can spot them at a glance.
Preparer (Priority 2)
Any value you type into the wizard or send via chat. This includes:
- Correcting an OCR misread (e.g., fixing "$12,345" that OCR read as "$12,245")
- Entering data from a phone interview
- Adding values for forms that have no uploaded document
Preparer values are protected. If the client uploads a new version of a document, the OCR extraction won't overwrite your corrections.
OCR (Priority 3)
Values extracted by the AI from uploaded documents. These are the initial values that populate form fields when a document is processed. They're accurate in most cases but can be corrected by entering a preparer value.
Upload (Priority 4)
Metadata that comes from the document classification itself rather than field-level OCR -- for example, the document type or the payer name derived from the upload context.
System (Priority 5)
Values computed by the tax engine's dependency graph. These recalculate automatically whenever upstream values change. Examples: AGI on Form 1040 Line 11, total tax on Line 24, self-employment tax on Schedule SE.
System values show a green overlay in the PDF prep view.
PDF Overlay Color Reference
The prep view uses colors to show the source of each field value at a glance.
| Color | Source | When You See It |
|---|---|---|
| Purple | Override | Preparer replaced a computed value |
| Blue | Preparer input / Upload | Preparer typed a value, or value came from upload |
| Rose | Spouse input | Spouse-specific field in MFJ returns |
| Green | Computed / OCR | Tax engine calculated it, or AI extracted it |
| Red | Error | Validation failure (missing required field, out-of-range value) |
| Amber | Prior year | Carried forward from a previous tax year |
| Gray stripes | Unsupported | Field exists on the PDF but is not yet supported |
Tip
Purple fields deserve extra attention during review. They represent places where the preparer overrode the engine's calculation -- make sure the override is still correct after all other data is entered.
How to Override a Computed Value
- Navigate to the field in the wizard (or click it on the PDF)
- The field shows the computed value with a green overlay
- Enter your value -- the source automatically changes to
override - The PDF overlay turns purple to indicate the override
- Downstream fields that depend on this value recompute using your override
To remove an override and revert to the computed value, clear the field. The engine recalculates and the overlay returns to green.
Duplicate Detection in Bookkeeping Handoff
When business receipts flow from quarterly bookkeeping into Schedule C at filing time, PaisaTax checks for duplicates using a 5% threshold.
The system compares bookkeeping-derived amounts against any values already on Schedule C (from direct document uploads or preparer entry). If an amount matches within 5%, it flags the potential duplicate for your review rather than silently double-counting.
Warning
Always review flagged duplicates before finalizing. A legitimate expense might appear in both a 1099-NEC upload (as gross receipts) and in bookkeeping (as tracked income). The system flags these so you can confirm the correct treatment.
Source Priority in Multi-Document Scenarios
When a client uploads multiple documents that affect the same field, the most recent extraction wins at the OCR level. But if you've already entered a preparer value, no amount of re-uploading will overwrite it.
Example: Client uploads a W-2, you correct Box 1 wages. Client then uploads a corrected W-2. The OCR extraction from the corrected W-2 won't overwrite your manual entry. You'll need to review the new document and update your entry if the corrected W-2 has different amounts.
This design prevents accidental data loss. The preparer is always in control.