Conference environment: no real charges. The mock gateway approves whole-dollar amounts and declines amounts with cents. The account-lookup form creates links but cannot deliver them to fictional email addresses or 555 phone numbers.
A secure window into the accounts your clients placed with you.
nativePortal gives each client a view scoped to its own accounts, with the account history, documents, and reporting context needed to audit the work. File uploads let clients send material back through the portal. Sign-in supports modern SSO and MFA.
Account access
Search and inspect only the portfolios available to that client.
Audit and reports
Review account activity, payments, documents, and client-specific information.
File exchange
Clients can upload material for your team in the production experience.
Explore the nativePortal demo →
The conference demo uses fictional accounts. Sign in as Jordan at Acme or Priya at Northwind to see how each client sees only its own book.
Try searching for Dana Whitfield under Acme, then Maria Castellano under Northwind. Account activity, payments, documents, and client-specific panels make the scope visible.
This demo is read-only: documents open, but uploads are disabled. Reporting and production upload access depend on the client configuration.
Latitude APIs and Workflow activities, connected. Built to move information when your process needs it.
Latitude API integrations
Use Native’s existing Latitude API work as the starting point. We confirm the specific API coverage and deployment fit for each integration.
API Request in Workflow
Call an external service from a Latitude Workflow. Send and wait, or hand the request to the background worker when the answer takes longer.
Insert Account Data
Add supported account records through a governed Workflow activity, including notes and selected contact details.
Update Account Data
Map a response into reviewed Latitude account or debtor fields, with scope and field choices visible before saving.
The callback service completes the loop
When an external service answers later, the listener authenticates and correlates the callback, stores its result, and raises a Latitude Workflow event. Workflow decides the next action.
See the callback flow →
A simple example: a Workflow sends a request for account review, then continues. The provider responds later.
1 · SendAPI Request submits the account context.
2 · ReceiveNative’s callback listener accepts and correlates the reply.
3 · ResumeA Latitude event starts the callback Workflow.
4 · ActWorkflow checks the result and uses its configured activities.
Illustrative flow only. This page does not send a request, start a listener, or change Latitude data.
Ask about your Latitude configuration. Get answers grounded in your environment.
Bring your configuration, Exchange Clients, Workflows, custom SQL jobs, stored procedures, and triggers into an isolated customer knowledge space. Ask how your environment is configured and where a rule lives.
Configuration knowledgeCustomer-isolated memoryNo live transaction queries
Preview nativeInsights
Simulated conversation using fictional configuration examples. No customer configuration is loaded, no AI service is connected, and no transaction database is queried.
DEMO CUSTOMER WORKSPACE · CONFIGURATION ONLY
Try a suggested question for a scripted answer with sample configuration sources. Other questions receive a demo scope response.
Keep your Latitude billing rules. Automate the repetitive work.
Set up customer billing rules, prove the results beside Latitude, and review exactly what matched. The screens below show the proof experience with fictional examples.
NATIVEINVOICE · PARALLEL PROOF PREVIEW
Illustrative screens only. Every customer, group, ID, amount, and result below is invented. This preview does not connect to a database or create invoices.
nativeInvoice
Read-only parallel proof
Prove NativeInvoice beside Latitude
Four guided steps, with no financial writes.
1Read configuration
Discover parent customers, groups, billing choices, and report mappings.
Read configuration
2Review what was found
Confirm inherited choices and approve exceptions before proof.
Show configuration
3Perform the parallel test
Calculate proposed invoices and create proof PDFs in a separate folder.
Perform read-only test
4Compare with Latitude
Inspect membership, amounts, dates, and reversal state after Latitude runs.
Compare results
Sample screen · proof only · no Latitude invoice IDs allocated
nativeInvoice
Customer setup
Review a group once
Apply common choices, then review parent-specific exceptions.
DEMO-GRP-01 · Northstar Practice Group
3 fictional invoice parents · Monthly, end of month · Native PDF output
Approved in this mockup
Shared billing choices
Direct payments: Include Exact reversal matching: Yes Replacement payment matching: Yes
Apply to group
Parent code
Fictional parent
Run plan
Review
DEMO-C1
Northstar Sample Services
Monthly · EOM
Ready
DEMO-C2
Willow Example Partners
Weekly · Wednesday
Ready
DEMO-C3
Bluebird Demo Office
Daily · weekdays
Exception review
Illustrative configuration · invented codes and names
nativeInvoice
Detailed proof
See what matched
A fictional comparison showing the kind of evidence available after a Latitude run.
Sample proof run
Cutoff: month end · 3 parent invoices · 3 PDFs created
Comparison status
3 exact matches · 0 differences · 0 missing PDFs
Parent
Invoice IDs
Payment UIDs
Amount A
Amount B
Tax
Result
DEMO-C1
1 / 1
48 / 48
$12,400.00
$2,100.00
$315.00
Exact
DEMO-C2
1 / 1
27 / 27
$7,850.00
$1,420.00
$213.00
Exact
DEMO-C3
1 / 1
19 / 19
$5,200.00
$940.00
$141.00
Exact
Preset demonstration values · no live calculation or customer records
In production, the planned operator flow is one run for all approved invoices due that day, including weekday, chosen-day weekly, and end-of-month schedules. The current install remains a read-only proof.
Start with the process. Find the path to a working Latitude Workflow.
Describe the outcome you need. Native helps separate the triggering event, the business meaning of each condition, the activities and paths, and the proof needed before a workflow is ready.
A faster starting point
See the proposed event and every path before building.
Make business rules explicit instead of guessing from phrases.
Review supported activities and open decisions together.
Test expected outcomes against observed Latitude behavior.
Four steps, one workflow workspace
UnderstandIdentify the trigger, context, action paths, and exceptions.
ResolveDetermine what the rules mean for this process and environment.
BuildChoose events and activities, then review the workflow design.
ProveCompare expected results with observed Latitude behavior.
The walkthrough uses fictional data. It does not analyze documents, generate a deployable Workflow, or run anything in Latitude.
Bring the specifications, samples, layouts, and context you have. nativeExchange helps identify the likely imports and exports, build reviewable shells for supported layouts, and surface the decisions needed before a working integration can be proved.
A faster starting point
See the proposed file inventory before building.
Review source layouts and what sample parsing proves.
Keep source names separate from business meaning.
Focus your time on the questions that affect behavior.
Four gates, one interface workspace
ShellsConfirm each inbound and outbound layout, then prove supported physical parsing.
Core mappingResolve business meaning before approving Latitude mappings.
Advanced behaviorReview processing rules, procedures, and customer-specific decisions.
Full testingCompare expected results with observed Latitude state and behavior.
Each interface has its own scope. A shell that loads or parses is not yet a business-validated integration. nativeInsights is an optional customer-specific layer; Native's shared knowledge is available without it.
LATITUDE
