Tuhund supports Excel upload as a controlled convenience feature, not as a replacement for normal system driven work. This distinction is fundamental to how the system preserves accuracy, accountability and operational discipline.
Excel upload exists to accelerate specific tasks where data already exists in structured form. It does not represent how work is intended to be performed inside Tuhund.
1. Excel is a data entry accelerator, not a business process
Regular work in Tuhund enforces
-
validations at every step
-
real time calculations
-
permissions and role checks
-
workflow and approval sequencing
-
audit trail creation
Excel upload bypasses the interactive process layer and injects data at a defined entry point. For this reason, it cannot and must not replace daily transactional work. If Excel were used as a primary interface, the system would lose its ability to control, validate and explain transactions.
Excel is therefore positioned as a helper, not a workflow.
2. Where Excel upload is available and widely used
Excel upload is enabled only in functions where its use is safe, logical and does not weaken downstream controls. In most cases, this means pre approval, non transactional or reference stage data.
Bulk enquiry entry
Enquiries are non financial and non stock affecting.
Excel upload is widely used when enquiries are received from exhibitions, distributors or marketing campaigns or during data migration.
The system remains safe because
-
no commitment is created
-
validations and duplicate checks still apply
-
workflows only begin after enquiry creation
Excel accelerates intake without bypassing any business logic.
Bulk lead creation
Leads represent potential business, not confirmed activity.
Excel upload is commonly used for
-
marketing sourced lead lists
-
imports from external CRMs
-
legacy system transitions
Safety is maintained because
-
leads remain inactive until worked inside Tuhund
-
assignment, ownership and status changes follow normal rules
-
conversion to enquiry or opportunity requires system actions
Excel speeds up onboarding while sales discipline remains intact.
Purchase order items before purchase order approval
Before approval, a purchase order is only a draft.
Excel upload is used when
-
vendors provide quotations in spreadsheet form
-
large BOM based orders are prepared
-
multiple pricing scenarios are consolidated
System integrity is protected because
-
approval is mandatory
-
taxes, totals and pricing are recalculated by the system
-
budget and permission checks occur at approval
Excel helps preparation, approval protects the system.
Sales order items before approval
Unapproved sales orders do not allocate stock or recognise revenue.
Excel upload is useful when
-
customers submit orders in Excel
-
large repeat orders are placed
-
contract pricing is applied in bulk
Controls remain intact because
-
validations re run after upload
-
credit limits and pricing rules apply at approval
-
dispatch and invoicing remain locked
Excel improves speed, approval enforces control.
Bulk entry of contact forms
Contacts are reference data.
Excel upload is widely used for
-
trade fair and exhibition data
-
website form exports
-
third party database imports
It is safe because
-
there is no financial or stock impact
-
duplicates and mandatory fields are validated
-
contacts only become active through user action
Excel reduces clerical effort without system risk.
Attendance upload (temporary or exceptional use)
Attendance data may originate outside the system.
Excel upload is allowed
-
before biometric or device integration
-
during device failure
-
for exceptional historical correction
Strict controls apply because
-
uploads are role restricted and time bound
-
verification or approval is required
-
payroll and compliance logic still runs normally
Excel acts as a bridge, not a workflow.
3. Why Excel cannot replace regular work
Many core Tuhund functions depend on live system state such as
-
current stock levels
-
batch and serial rules
-
costing and valuation timing
-
approval hierarchies
-
inter module dependencies
Excel contains static values. It cannot react to real time conditions. Allowing Excel as a substitute would lead to incorrect valuations, broken stock integrity and silent rule violations.
For this reason, Excel upload is disabled wherever system state and cascading effects are critical.
4. Auditability, security and accountability
Regular transactions in Tuhund automatically generate
-
timestamps
-
user attribution
-
traceable references
-
system derived values
Excel files are external artefacts. Overuse would weaken audit trails, blur responsibility and increase reconciliation effort. Excel upload is therefore restricted to areas where accountability remains clear and verifiable.
5. Design principle summary
Excel upload in Tuhund follows a consistent rule set
-
it is optional, never mandatory
-
it is allowed only where misuse cannot damage system integrity
-
it is commonly enabled before approvals, never after
-
it complements workflows, it does not replace them
In short, Tuhund is a process driven ERP, not a spreadsheet driven system. Excel is supported to improve efficiency but control, validation and governance always remain inside the system.
