Accrella

Article ·

Replace your tax lien spreadsheet: column map and switching checklist

A free tax lien research tracker, an exact owned-lien import column map, and a practical test for deciding when tax lien software should replace a spreadsheet.

In this guide

Replace your tax lien spreadsheet when maintaining the file starts obscuring which certificates you own, what you paid, and what needs review next. The migration should preserve those answers before adding anything else. Start with the free CSV below, separate research candidates from purchased certificates, and preview a small owned-lien batch before moving the rest.

This guide combines the software-versus-spreadsheet decision with the migration itself. Product behavior and the linked source references were checked on October 10, 2026. The column map describes Accrella’s owned-lien importer; it does not turn an arbitrary county auction list into purchased positions.

Tax lien software vs. spreadsheets: when to switch

There is no defensible universal certificate count at which Excel stops working. A single reviewer with consistent source files can manage a different workload from a team reconciling several counties. Use a workflow threshold instead: move to a shared portfolio system when any essential control below repeatedly fails despite a documented spreadsheet process. This is our editorial decision framework, not a measured industry benchmark.

A practical switching test
ControlSpreadsheet still works whenConsider switching when
OwnershipPurchased certificates are clearly separated from research.Auction candidates and owned positions get mixed together.
ReconciliationCertificate count and money totals reconcile to purchase records.You repeatedly rebuild balances or discover duplicate rows.
HandoffsThe next reviewer can find the supporting record and next action.A handoff depends on the original researcher’s memory.
DatesEvery important date has a named event, source, and reviewer.A generic expiration column drives decisions without explaining the event.
MaintenanceOne controlled file remains current.Conflicting copies or manual status checks consume the review meeting.

If those controls still work, keep the spreadsheet and improve its evidence columns. If they fail, test software against your own troublesome records rather than a perfect demo file. The acceptance test is whether another person can reconcile the imported positions and explain their next review, without asking you what an unlabeled cell meant.

How to use the free CSV tracker

The download contains headers only, with no example investment or invented owner data. It combines import-ready portfolio columns with research-only columns: recordType, sourceUrl, sourceCheckedAt, researchStatus, nextReviewAt, reviewer, and researchNotes. Use recordType to distinguish RESEARCH from OWNED in your working copy. Before importing, filter to certificates you actually own and create a separate file containing only the mapped portfolio columns below. The research columns are your working tracker, not additional Accrella portfolio fields.

Keep a read-only original and a dated migration copy. Import the CSV into your spreadsheet with certificateNumber, parcelId, countyFips, and zip treated as text. Microsoft documents that Excel can remove leading zeros and lose precision in long numbers; formatting after that conversion cannot reconstruct a damaged identifier. Look up the county’s full geographic code in the Census Bureau code lists rather than inventing a code from its name.

Owned-lien import column map

Use these exact headers for the clean import file
HeaderRequirement and meaningRecommended format or check
certificateNumberRequired: the certificate identifier.Text; retain the county’s identifier and check the preview.
parcelIdRequired: the property’s parcel identifier.Text; preserve leading zeros and meaningful punctuation.
countyFipsRequired in the row or supplied as a batch default.Five digits, stored as text; county name alone is insufficient.
stateCodeRequired in the row or supplied as a batch default.Two-letter state abbreviation, such as FL.
faceValueRequired: certificate principal, not assessed property value.Positive amount, such as 1200.00.
purchasePriceOptional in validation, important for reconciliation.Actual positive amount paid; blank defaults to faceValue with a warning.
purchasedAtRequired in the row or supplied as a batch default.YYYY-MM-DD; actual acquisition date.
statutoryInterestRateRequired in the row or supplied as a batch default.Awarded or accounting accrual rate; use an explicit percentage, such as 1% or 0%.
propertyTypeRequired.residential, commercial, or vacant.
taxYearsRecommended; participates in duplicate identification.A year or range, such as 2024 or 2023-2024.
ownerNameRecommended.Owner from the supporting record; do not guess.
propertyAddress, city, zipOptional address components.Blank propertyAddress uses a parcel placeholder; review that warning.
lifecycleStateOptional workflow status.Omit for the default PURCHASED; verify any supplied supported status.
redemptionWindowExpiresAtOptional recorded redemption-window date.YYYY-MM-DD only after verifying the event; leave unknown dates blank.

Despite the field name statutoryInterestRate, use the certificate’s awarded or accounting accrual rate, not automatically the state maximum. The importer accepts percentage and decimal forms. Explicit percent signs avoid a material ambiguity: 1% means one percent, while a bare 1 is interpreted as the decimal fraction for one hundred percent. A genuine zero-rate award can be entered as 0%; missing rate data is not the same thing.

Aliases such as cert #, parcel #, lien amount, and purchase date are recognized, but renaming to the exact headers makes review simpler. A recognized “amount” header does not prove its contents are certificate principal. County exports may use that word for a minimum bid, balance due, or property value. Confirm the meaning before copying it into faceValue.

Run a small preview, then reconcile

  • Create a clean batch with owned certificates only. Use CSV, TSV, or XLSX; legacy XLS is unsupported. Current intake limits are 25 MB and 1,000 rows per file.
  • Use batch defaults only when they truly apply to every row. Check the state selection, especially for a mixed-state file; include row-level state and county values when they differ.
  • Preview before committing. Inspect READY, REJECTED, and DUPLICATE rows, plus non-blocking warnings about substituted purchase prices or missing addresses.
  • Check identifiers, tax years, dates, and rates against the purchase record. Do not fix a rejected row by inventing an owner, property type, or date.
  • Commit the reviewed ready rows, then reconcile the accepted, rejected, and duplicate counts. Total accepted face values and purchase prices separately against the selected source records.

Duplicate checks use certificate number, county, and normalized tax years within the organization. Parcel ID alone is not the duplicate key. Missing years can therefore undermine your reconciliation even though they are recommended rather than mandatory. Keep rejected and duplicate rows in an exception file until each has an explanation; a completed import does not mean every submitted row became a position.

Finish the migration without losing the research

Keep the original workbook, purchase confirmations, and research URLs together. CSV carries cell values, not your workbook’s comments, color rules, or supporting documents. Move the practical meaning of a red or yellow cell into researchStatus and researchNotes before exporting. Record which file and batch produced the accepted portfolio rows so the next reconciliation starts from a known baseline.

Accrella can preview and import these owned positions and show portfolio attention items tied to recorded dates. That does not validate the legal meaning of an imported redemption deadline. Keep eligibility, notice, and owner-redemption events distinct; the deadline guide below shows why a single national formula fails.

Sources and review method

Recommendations reflect the workflows described in these sources. Vendor features, plans and county availability can change; confirm the current scope with each provider.

‹ All insights