B2B Software Consulting in Dallas
Dallas–Fort Worth groups rarely run one company, and Texas Tax Code §171.1014 forces every affiliated entity in a unitary business onto one combined franchise report. ERPStack is remote-first, building that entity-aware ledger on PostgreSQL in Google Cloud us-south1, inside Dallas.
Quick Answer
In short: a Dallas–Fort Worth group's problem is entity count: combined franchise reporting under Tax Code §171.1014, one 1.75% single local use tax rate, and TDPSA scope with no revenue threshold. ERPStack builds multi-entity ERP on PostgreSQL in Google Cloud us-south1, physically Dallas and about 4 ms across the metro, with FMCSA hours-of-service retention built in.
Regional Compliance
- Combined franchise reporting, Tax Code §171.1014
- TDPSA (Bus. & Com. Code ch. 541)
- Texas Insurance Code §601.052 (GLBA safeguards)
- FMCSA hours-of-service records, 49 CFR §395.8
- Single local use tax rate, 1.75%
Security & Compliance Architecture
Dallas compliance is a matrix: one privacy statute, one tax code, two regulators.
TDPSA scopes the subsidiary, not just the parent
Bus. & Com. Code §541.002 measures each entity against SBA size standards, so a small Dallas subsidiary of a large group is in scope. Consent lives once in PostgreSQL and replays into Salesforce and the CRM.§521.053 runs two clocks at once
Individual notice by the 60th day after determination, notice to the Attorney General within 30 days once 250 Texas residents are affected, and a 10,000-record trigger for credit bureaux.Sales tax stacking versus the 1.75% election
Texas charges 6.25% state plus up to 2% local; a remote seller may elect the 1.75% single local use tax rate. A Dallas order-to-cash schema stores both, validated by Zod against a $500,000 nexus test.
Engineering Blueprint
Dallas is the rare US metro where the local cloud choice is real: Google Cloud us-south1 is a full region in the city, not an edge, so the Dallas PostgreSQL primary, Drizzle ORM schema and Next.js API stay inside Texas.
Peering at 1950 North Stemmons Freeway
DFW interconnection concentrates in carrier-neutral facilities such as Equinix DA1. We terminate the Dallas VPC there, cross-connect to us-south1, and keep AWS us-east-1-dfw-1a as the REST and Redis edge.
One combined franchise report
Tax Code §171.1014 makes an affiliated unitary group a single taxable entity, so every Dallas journal line carries an entity id and intercompany flag.
export const journalLine = pgTable('journal_line', {
entityId: uuid('entity_id').notNull(),
combinedGroupId: uuid('combined_group_id'),
intercompany: boolean('intercompany').default(false),
});Fleet and 3PL record retention
49 CFR §395.8(k) keeps hours-of-service records six months, so Dallas logistics clients stream ELD events through Apache Kafka into TimescaleDB, then post append-only Postgres rows under an Immutable Audit Trail.
Evaluate Your Stack
Take our interactive audit to see if your architecture is ready for operational scale.
Start Free AuditRegional Infrastructure
Infrastructure Region
Latency Metrics
Primary Datacenter
Success Stories in Dallas
Field Operations & Compliance Portal
Unified operational portal for field tracking and compliance
Read Case StudyTarget Industries in Dallas
Frequently Asked Questions
One. Texas Tax Code §171.1014 requires taxable entities in an affiliated group engaged in a unitary business to file a combined group report instead of individual reports, and treats that group as a single taxable entity. Consolidate before apportionment: one combined report for the whole Dallas group.
Google Cloud us-south1, with zones us-south1-a, us-south1-b and us-south1-c. AWS runs no Texas Region but operates the Dallas Local Zone us-east-1-dfw-1a off us-east-1, and Microsoft Azure southcentralus sits in Texas. Of the big three, only Google names a Texas city.
SAP S/4HANA wins on statutory ledgers in several countries; Oracle NetSuite wins on speed to first close. For a Dallas group that is multi-entity but single-country, §171.1014 combined reporting is a few thousand lines — a PostgreSQL ledger on Drizzle ORM costs less than a Microsoft Dynamics 365 renewal. Buy the CRM, build the ledger.
Dallas peering concentrates in carrier-neutral facilities such as Equinix DA1 at 1950 North Stemmons Freeway. Putting the API tier in Google Cloud us-south1 and cross-connecting there holds a Dallas branch within single-digit millisecond RTT of the database; us-east-1 adds 30 ms.
The Texas Department of Insurance. Texas Insurance Code §601.052 directs TDI to implement the safeguards standards required by 15 U.S.C. §6805(b), the Gramm-Leach-Bliley security rule. For a Dallas carrier that makes encryption, RBAC and SSO examinable by a state examiner.
A remote seller may elect Texas’s single local use tax rate of 1.75% instead of stacking destination rates on the 6.25% state rate. Dallas sellers shipping statewide carry both models, plus the $500,000 safe-harbour test.
At least six months. Under 49 CFR §395.8(k)(1) a motor carrier retains records of duty status and supporting documents for not less than six months from receipt, and the driver keeps the previous seven consecutive days. Dallas fleets need immutable ELD ingest.