Keep your existing systems.
Extend what you need.
Connect SAP, LandSoft, Phoebus, SouthTelecom, PosApp and your other existing systems. The data scope is designed around your business processes.
| System | Related scope | Business & data | Clarified per project |
|---|---|---|---|
 SAP / SAP S/4HANA | Booking · CRM · CPMS · Purchasing / Workflow | Two-way sync: township, project, unit, booking, contract, payment schedule, receipt, payment voucher, receivables. | Data is kept consistent between SAP and Pico; the sync schedule is agreed per project. |
 LandSoft | Booking → CRM (Nam Long) | In the first phase, bookings sync to LandSoft. Pico CRMCRM: Customer, contract & receivables management then fully replaces LandSoft. | Data migration and reconciliation follow an approved plan. |
 Phoebus | CRM (Sơn Kim Land) | CRMCRM: Customer, contract & receivables management syncs customer contracts, receivables, receipts and payment vouchers to Phoebus ERP for accounting. | Sales run on Pico CRMCRM: Customer, contract & receivables management and accounting on Phoebus, with no re-entry. |
 SouthTelecom | Living · Customer and resident requests | Requests are logged in Living and forwarded to SouthTelecom; the connection sends information via Zalo and SMS. | Request categories, handling flows and notification channels are agreed per business process. |
 PosApp | Loyalty · Voucher · Event (Nam Long) | Vouchers issued on Pico are synced to PosApp so customers can redeem them at stores in the township, for example The Aji restaurant at Waterpoint. | Offers include percentage discounts, cash discounts or gifts. |
| Other systems | As needed · VCB · MoMo | Connections can extend to existing systems and payment channels as the business needs. | Connectivity, access rights and operating responsibilities are assessed before scope is finalized. |
Logos are used only to identify systems and do not imply an official partnership with the vendor.
Touchpoints, business logic,
existing systems.
Select a layer to see its role in the model.
Customers, residents and staff interact through touchpoints designed for each role.
Every connection needs four answers
- 01
Primary source
Which system owns the source data?
- 02
Data flow
Which objects, in which direction, and when do they sync?
- 03
Reconciliation
Which rules govern discrepancy checks and error handling?
- 04
Responsibility
Who operates, monitors and coordinates when an incident occurs?
Not a diagram on paper.
Data that is running.
-
Sơn Kim Land CRM Pico → Phoebus ERP Contracts, receivables and receipt and payment vouchers created in CRM are synced to Phoebus. Sales and accounting share a single source of figures. -
Nam Long Loyalty · Voucher · Event → PosApp Vouchers received through NL Club or events can be redeemed right away at the stores in the township, such as The Aji restaurant at Waterpoint: percentage discounts, cash discounts or gifts. -
Businesses using SAP SAP S/4HANA ⇄ Booking · CRM · CPMS · Purchasing Two-way sync of township, project and unit data, bookings, contracts, payment schedules, receipt and payment vouchers and receivables, so both systems always match.
Which data. Which source.
Which direction. When.
Select a system to see its confirmed scope.
SAP / SAP S/4HANA
- Related Pico products
- Booking · CRMCRM: Customer, contract & receivables management · CPMSCPMS: Building operations management · Purchasing / Workflow
- Data / business scope
- Township, project, unit, booking, contract, payment schedule, receipt, payment voucher, receivables.
- Primary data source
- Data is kept consistent between both systems, object by object.
- Exchange direction
- Two-way: SAP ⇄ Pico.
- Timing
- Scheduled or real time.
What data is exchanged?
Each connection has its own list of data objects (customers, products, contracts, receivables, requests, purchasing documents…). The list is finalized in the integration design document before build.
Which system is the primary data source?
Each data object has one primary source. Live examples: at Sơn Kim Land, Pico CRMCRM: Customer, contract & receivables management is where contracts, receivables, receipts and payment vouchers originate, and they sync to Phoebus for accounting; at Nam Long, vouchers are issued on Pico and synced to PosApp.
One-way or two-way sync?
It depends on the connection. With SAP, Pico syncs township, project, unit, booking, contract, payment schedule, receipt, payment voucher and receivables data in both directions. With Phoebus and PosApp, data flows one way, from Pico outward.
When a sync fails, who monitors and resolves it?
Each side's point of contact, how errors are logged, how data is reconciled and the resolution deadline are written into the integration design and operating agreement, not left to default.
Can we keep our existing system and deploy in phases?
Yes. Sơn Kim Land keeps Phoebus for accounting and uses Pico CRMCRM: Customer, contract & receivables management for sales. Nam Long started with Booking synced to LandSoft, then moved to Pico CRMCRM: Customer, contract & receivables management.
Does integration capability mean certified partnership?
No. Integration capability means a technical connection that has been confirmed; it does not imply that Pico is a certified partner of the vendor.
Which systems are you running?
Prepare a list of your systems and the connections you need. Pico will work with you to clarify the scope of the data exchange.