ATLAS Form

i

Use aliases or last four digits only. Never enter passwords, API secrets, private keys, full account numbers, or employee-level payroll data.

Products in scope *

✓Atlas XTreasury, banking and cash intelligence✓Atlas CFinance operations and close intelligence

Engagement overview

Client legal name *Client trade nameHeadquarters *Operating regionsIndustryTarget go-live

Business objectives and desired outcomes *What should Atlas improve, automate, consolidate, monitor, or report?Success measuresCoverage, reconciliation time, data freshness, close time, error rate or adoption.

Primary contacts

Executive sponsorProject owner *Project owner email *IT / integration lead

i

List the tools your teams use today. Product names are enough—for example, NetSuite, SAP, Workday, Manhattan, Shopify or Snowflake.

Current system landscape

Banking / treasury systemsTools used to view cash, manage bank accounts or make payments.ERP / accountingYour main finance and accounting platform.Payroll / HCMSystems used for payroll, benefits and employee records.Billing / paymentsTools used to create invoices, collect money or process payments.Inventory management systemThe system that tracks products, materials, quantities and stock levels.Warehouse management system (WMS)The system that manages receiving, storage, picking, packing and shipping.Data warehouse / lakeA central place where information is stored for reporting and analysis.Integration / ETL platformA tool that moves and synchronizes data between systems.

Current data movementExplain what information moves between systems, how often, and by what method.Known data-quality issuesExamples include duplicate records, missing information, late files or totals that do not match.

i

Aggregate values or ranges are welcome when exact financial values are restricted.

Treasury and banking profile

Financial institutionsCountriesActive accountsPrimary currenciesAverage transactions / dayPeak transactions / day

i

API means systems connect automatically. SFTP means secure files are exchanged. SWIFT is a bank messaging network. Portal/manual means a person downloads or uploads files.

Formats, exceptions and controlsBAI2, CAMT, MT940, NACHA, ISO 20022, reversals, duplicates, sweeps and entitlements.

i

Provide aggregate payroll counts only—never employee names, compensation, bank details or tax identifiers.

Finance operating model

ERP / product / versionEntities / ledgersChart of accounts sizeClose durationPayroll provider(s)Employees / contractors (aggregate)

Normal and peak volumesInclude cadence for journals, invoices, payments, expenses, payroll summaries and master-data changes.Manual processes and workarounds

i

API/SOAP are direct system connections. A webhook sends an update when something happens. File transfer moves scheduled files. Warehouse share gives controlled access to analytics data. iPaaS/ETL tools connect and transform information.

Authentication standardsHow systems confirm that a user or connection is allowed.Target cadence / SLAHow often data should update and the expected delivery time.Network controlsRules such as VPN, private links, firewalls or approved IP addresses.Retention requirementsHow long records, source files and activity logs must be kept.

Architecture notes and constraintsRequired tools, prohibited methods, technical limits or important dependencies.

Highest classification in scope

PublicInternalConfidentialRestricted / highly sensitive

i

PII identifies a person. PCI relates to card payments. Data residency controls where information may be stored. SSO lets employees use their company login. SCIM automates user access. SIEM collects security activity.

Data residency requirementsCountries or regions where information must—or must not—be stored.Regulatory obligationsLaws or standards your organization must follow.Identity provider / SSOYour company login system, such as Microsoft Entra ID or Okta.Provisioning / SCIMHow user accounts are automatically created, updated and removed.Audit logs / SIEMWhere security and user-activity records are reviewed.Incident notification requirementHow quickly Lexington must notify you of a confirmed security issue.

Required security review artifactsDocuments your team needs before approval, such as a questionnaire, SOC report, DPA or architecture review.

Target kickoffTarget pilot / UATTarget production go-liveBlackout periods

Top risks, dependencies and decisionsSupporting materials availableLexington will coordinate secure transfer separately.

Client confirmation

I confirm that the information in this packet is complete and accurate to the best of my knowledge, is appropriately authorized for disclosure to Lexington for Atlas implementation planning, and will be updated if material assumptions change.

I am authorized to submit this information.

Authorized representative *Title *Email *Date *

Electronic signature *Typing your name constitutes your electronic signature for this onboarding submission.

i

The NDA should be added only after Lexington counsel completes and approves the legal placeholders in the source agreement.