In-App Parsing vs. Excel Add-in: which should I use?

Overview

If you're on the Pro plan, you have two options for parsing Rent Rolls and T12 Operating Statements:

• In-App Parsing — review and confirm mappings inside the Archer web application before your underwrite is generated
• Excel Add-in — run the underwrite first and review mappings inside Excel after the file is generated

Both approaches read the same source documents and produce the same output in your underwrite model. The difference is where the review and correction steps happen, and when.

Starter plan: In-App Parsing is the only parsing method available. The Excel Add-in is a Pro plan feature.

How each approach works

In-App Parsing You upload your files in the Run Underwrite modal with the "Use in-app parsing" checkbox enabled. Archer guides you through a step-by-step review of column mappings, charge codes, floor plans, and financial categories inside the browser. Once you confirm each step, Archer generates your underwrite. You see Rent Roll and Financial analytics — benchmarked against market comps — before the Excel file is created.

Excel Add-in You upload your files and run the underwrite without the in-app workflow. Archer processes the files in the background and delivers a completed Excel file. You then open the file in Excel and use the Add-in to review and correct any parsing mappings directly inside the model. When done, you must Save to Archer from Excel for the activity to sync back to Archer and appear in All Activity.

Comparison

When to use In-App Parsing

• You are starting a new underwrite and want to validate your data before the Excel file is generated
• You want to see Rent Roll and Financial analytics benchmarked against market comps before committing to an underwrite
• You are not working in Excel yet and prefer to stay in the browser

When to use the Excel Add-in

• You have already generated an underwrite and receive a revised Rent Roll or T12 mid-deal
• You are actively working inside the Excel model when the new file arrives and want to parse without switching back to the browser
• Your team has an established workflow built around the Add-in

You can mix both approaches

You are not locked into one method for a given deal. A common pattern for Pro customers:

1. Run the initial underwrite using In-App Parsing to validate data and review analytics upfront
2. Receive a revised file later in the deal while working in Excel
3. Parse the update directly in Excel using the Add-in, since you're already in the model
4. Save to Archer from Excel so the updated activity syncs back to All Activity

Save to Archer — a required step for Excel Add-in activity

When you use the Excel Add-in, activity does not automatically sync back to Archer. You must explicitly Save to Archer from within Excel for:

• The underwrite or parse to appear in All Activity
• Archer to use the updated parsed data for Rent and Expense Comps
• In-app analytics to become available for that parse

If you expect to see Excel Add-in activity in All Activity and it is not there, Save to Archer is the most common reason it is missing.

Changing the default

The "Use in-app parsing" checkbox in the Run Underwrite modal is enabled by default for Pro customers. You can uncheck it on any individual underwrite to use the Excel Add-in flow instead.

If your team predominantly uses the Excel Add-in and you want the checkbox off by default for all users, this can be configured at the account level. Contact your Archer administrator or Archer support to update this setting.