Document management and correspondence for BUMN

In an Indonesian state-owned enterprise (BUMN), one letter can pass through the corporate secretariat, several directorates, a division head and the unit that does the work before anyone replies. Each hand-off produces a paper disposition sheet, a chat message or a forwarded email, and when a review arrives, people have to piece the story together from all of them. This page describes the document problems that come up most often in a BUMN, shows how Obscura handles them and explains where the system can run.

Document problems that come up often

The problem is rarely one big failure. It is usually a handful of small habits that pile up.

• High letter volume and layered disposition. Incoming letters move from the board to a director, then to a division head and a unit. While disposition lives on paper or in chat, nobody knows exactly where a letter is or who has read it.
• Layered approvals that stall when officials travel. A document waits for a director who is on an official trip, and work stops until someone sends a reminder or decides outside the system.
• Confidential board and RUPS files. Meeting materials circulate as email attachments and downloaded copies, so it is hard to know who ever held a particular copy. RUPS is the general meeting of shareholders.
• Preparing for a review. An auditor asks who saw and approved a document, and the answer has to be collected from several applications and inboxes.
• Many subsidiaries and units. Each entity has its own structure and access rules, yet the parent company still needs to manage them consistently.

Four common workflows

The scenarios below are illustrations. We adapt the real scope to your documents, your organisation chart and the controls you already use.

1. An incoming letter through to a sent reply

1. The secretariat receives the letter and registers it. Obscura assigns an agenda number, and scanned letters become searchable because OCR runs at registration.
2. The president director gives disposition to a director, with an instruction and a deadline. Disposition can go to a user or to a position.
3. The director passes the letter to a unit head. The task and the read access travel together, and both are withdrawn if the routing changes.
4. The unit drafts the reply from an approved letter template, so every unit uses the same letterhead and layout.
5. The reply enters an approval route, receives its number, is signed and is filed. Obscura records when the letter was sent, while delivery itself still goes through your usual email, courier or other approved channel.

Every instruction can be traced back to the decision behind it, and anyone can see where a running letter stands without asking several people.

2. Layered approvals with delegation

You set the approval route once for each document type, for example drafter, division head, finance director and then president director. Tasks go to positions, so a new officeholder receives the work at once and nobody rebuilds the route.

When a director travels, you can name a substitute for a set period and only for the actions you allow. The substitute can decide, and the record still shows who actually approved. If a deadline passes, the task follows the escalation path you defined. Each approver can approve, reject or return the document for revision, and every decision is kept with its note.

A change to the route applies to new work. Documents already in progress keep the route they started with.

3. Confidential board and RUPS documents

Materials for board meetings or the RUPS are stored with access that matches responsibility. You decide who can view and who can change each document, with allow and deny rules inherited from the parent folder.

• Documents are read in a secure image-based preview, and downloads can be blocked by classification. Every view carries a watermark with the reader's identity.
• The Secure Folder module encrypts the folders that hold your most sensitive documents. Each folder has its own key, and each decryption is checked against the person's identity and recorded in the audit trail.
• When a copy must be shared, the link can have a password or an email OTP and an expiry date, and you can revoke it at any time. Access to the link is logged.
• With the Watermarking module, each download or shared copy carries an invisible mark for its recipient, and an issuance ledger links the file, the version and the recipient. If a copy turns up where it should not be, your team can check who it was issued to. Tracing works best on the original file or on a clear screenshot that shows about two paragraphs of body text. Photos of a screen are not supported.

4. Ready for a review

Each document carries its own history of changes, decisions, signatures and activity. When an auditor asks who saw or approved a document, the answer is on the document and does not have to be assembled from email. The audit log uses a cryptographic hash chain that helps detect changes to the log itself, so the record can be checked again years later.

Obscura supplies the evidence and the trail. Whether a process meets a particular rule remains a judgement for you and for whoever reviews it. Retention schedules and legal holds are also available to support your records policy, and we confirm the scope with you before the pilot starts.

Signatures and e-Meterai

Obscura has two signing tiers. The internal signature uses Obscura's own certificate authority and timestamp service, and verification can detect any change made to the file after signing. This method is not PSrE-certified, so it fits internal memos and approvals where your policy accepts it. Certified e-signatures and e-Meterai go through a connected PSrE provider and a connected e-Meterai provider, and both need the e-sign module. We confirm the providers with you during the assessment.

Holdings, subsidiaries and units

If you serve several companies or units, the Enterprise edition runs the multi-tenant platform in your own cloud, and an operator panel manages the organisations or units on it. Each organisation or unit keeps the same separation as on Obscura Cloud, with its own database schema, subdomain, passkeys, signing certificate authority, audit-chain key and file storage namespace. A subsidiary then works in its own space while the platform is still managed in one place.

Where Obscura runs

• Obscura Cloud, run by Valid in Indonesia. Each organisation is a separate tenant, which suits teams that want to start without managing infrastructure.
• Your own cloud. Obscura is installed in your cloud environment, and we recommend AWS. Your team runs it.
• On-premise or a closed network, by special arrangement. The core system, workflows, repository, audit history and local services can run on your own servers or on a network with no outside access. Your team looks after its own servers and network. Services that come from an outside party, such as PSrE and e-Meterai providers, still need a connection that you approve.

For sign-in, Obscura supports local accounts or SSO through OIDC, plus LDAP, Active Directory and SCIM. The modules work the same wherever Obscura runs, and you license the modules that match your needs. The Correspondence and e-sign modules, for example, are licensed separately from the core system.

Start with one workflow

Pick the type of letter that stalls most often, for example an incoming letter that needs disposition across several directorates. We run it through Obscura with your team and then look at how much manual work disappears, how clear responsibility is at each step and what evidence remains at the end. That becomes the basis for a pilot. To talk it through, reach us on the contact page.

Learn more: correspondence and numbering, approvals and e-signatures, document control, watermarking and copy tracing, security and deployment options. For the basics, see the guides on the incoming letter agenda and disposition and on incoming and outgoing letter apps.